I generally rely on the breadcrumbs to form the context for the "question" and have nested #sr blocks under it.
Example
* Topic #sr
** One line definition of the topic
** Theorem #sr
*** Theorem statement in latex
*** Derivation #sr
**** The derivation in latex
In the above case, when the topic card answer is shown, I want it's children to be collapsed, so that I don't peek into the cards in it's children. I can restructure the cards such that the definition has a separate title and card is added there instead of on the Topic line, but I feel that's redundant as the breadcrumbs by themselves provide the context for me.
I think this would involve just calling a roam api to collapse the children when the answer card is shown? I would be willing to give a pull request if someone points to the roam api and appropriate place to call it in the current codebase. (been long since I worked on javascript projects).
I generally rely on the breadcrumbs to form the context for the "question" and have nested #sr blocks under it.
Example
In the above case, when the topic card answer is shown, I want it's children to be collapsed, so that I don't peek into the cards in it's children. I can restructure the cards such that the definition has a separate title and card is added there instead of on the Topic line, but I feel that's redundant as the breadcrumbs by themselves provide the context for me.
I think this would involve just calling a roam api to collapse the children when the answer card is shown? I would be willing to give a pull request if someone points to the roam api and appropriate place to call it in the current codebase. (been long since I worked on javascript projects).