Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Visually discriminate between domain entities and mechanics-related entities #7

Open
orolle opened this issue Nov 30, 2018 · 0 comments

Comments

@orolle
Copy link

orolle commented Nov 30, 2018

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

  • 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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant