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
Visually separate entities of the domain and implementation-specific mechanics. The seperation should be visually so that a developer and domain expert can see inter-dependencies between domain and mechanic-related entities easily and maybe hide detail by collapsing all entities into one high level component-grouping.
A :visualizer-tag :visualizer/background "#123456" for an entity
A :visualizer-tag for domain and mechanics: :visualizer/component :domain, :visualizer/component :lacinia-query, :visualizer/component :lacinia-pagination.
Provide domain / mechanic tag in hodors model definition :component :domain, :component :lacinia-query
(I have no idea which might be the best choice in the long term)
The text was updated successfully, but these errors were encountered:
Visually separate entities of the domain and implementation-specific mechanics. The seperation should be visually so that a developer and domain expert can see inter-dependencies between domain and mechanic-related entities easily and maybe hide detail by collapsing all entities into one high level component-grouping.
Visualization Alternatives
Model Alternatives
:visualizer/background "#123456"
for an entity:visualizer/component :domain
,:visualizer/component :lacinia-query
,:visualizer/component :lacinia-pagination
.:component :domain
,:component :lacinia-query
The text was updated successfully, but these errors were encountered: