Hodur is a domain modeling approach and collection of libraries to Clojure. By using Hodur you can define your domain model as data, parse and validate it, and then either consume your model via an API or use one of the many plugins to help you achieve mechanical results faster and in a purely functional manner.
MIT License
21
stars
7
forks
source link
Visually discriminate between domain entities and mechanics-related entities #7
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)
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