useAsyncData in composables that uses each other
Hi, everyone! 
I have a repo here: https://gitlab.com/HIV/budgettracker
The description:
I have a composable
Both of them are supposed to run server-side on initial load.
(B) uses (A) to compute
(B) is used on
the
The problem:
Whenever the app starts, it issues 2 requests to
What did I try:
1. use pinia store to join (A) + (B) data inside in one shot;
2. use closures in (A) and (B) to not to create two separate instances of (A);
3. use
If I use only (B) inside
The question:
What are the options to 'tear apart' single composable with
Thank you!
I have a repo here: https://gitlab.com/HIV/budgettracker
The description:
I have a composable
useTransactionGroupsuseTransactionsBoth of them are supposed to run server-side on initial load.
(B) uses (A) to compute
groups(B) is used on
transactionsTFilterthe
transactionsuseAsyncDatauseStateThe problem:
Whenever the app starts, it issues 2 requests to
transactionsTFilter -> (A): filtersTransactions (page) -> (B): groups -> (A): transactionsWhat did I try:
1. use pinia store to join (A) + (B) data inside in one shot;
2. use closures in (A) and (B) to not to create two separate instances of (A);
3. use
useSatateIf I use only (B) inside
transactionsfiltergroupsThe question:
What are the options to 'tear apart' single composable with
useAsyncDataThank you!
