You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I interpret the documentation in https://github.com/soulspace-org/overarch/blob/main/doc/usage.md#dynamic-views-dynamic-view in such a way that relations in the :ct vector of the :dynamic-view should have their :index automatically set by the position within the vector and that this information is used in the c4 plantuml rendering. However with overarch 0.29.1 the ordering seems to be random and the only option to get the expected output is to provide the :index property explicitly for each relation. This is quite tedious especially if relations are added or removed or the order of the calls changes.
The text was updated successfully, but these errors were encountered:
The :index attribute is a bit of a workaround to provide a stable ordering of the relations with all the set magic involved in calculating the content of a view. This situation is not ideal and I'd like to change the behavior for dynamic-views to keep the ordering of the :ct vector (auto-indexing). But on the other hand I'd like to keep the content calculation as simple as possible, in the context of selections and includes. So I have to think a bit about a solution that is not too specific and complex.
Currently I don't use dynamic views much, but I'm experimenting with them to see, if they are a way to visualize domain stories.
Could you tell me a bit more about your usage of the dynamic views and Overarch in general, so that I get a better understanding for your context? I've created a #overarch channel on the Clojure slack for discussions. You can also contact me via direct message there.
I interpret the documentation in https://github.com/soulspace-org/overarch/blob/main/doc/usage.md#dynamic-views-dynamic-view in such a way that relations in the :ct vector of the :dynamic-view should have their :index automatically set by the position within the vector and that this information is used in the c4 plantuml rendering. However with overarch 0.29.1 the ordering seems to be random and the only option to get the expected output is to provide the :index property explicitly for each relation. This is quite tedious especially if relations are added or removed or the order of the calls changes.
The text was updated successfully, but these errors were encountered: