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

Implement clustering by namespace #205

Merged
merged 1 commit into from
Aug 10, 2016

Conversation

bstegmaier
Copy link

Resolves issue #156

Enabling clustering will create subgraphs in graphviz. Clustering is based on the topmost namespace/module name.

Example

With clustering enabled all Recipe::* models will all be sorted into a 'Recipe' cluster.
Please note, that this simply a made up example and not production app.

Without clustering:
standard

With clustering:
clustering

Enabling clustering will create subgraphs in graphviz. Clustering is
based on the topmost namespace/module.
E.g. Recipe::Ingredient, Recipe::Step, Recipe::Step::Translation will
all be sorted into a 'Recipe' cluster.
@kerrizor
Copy link
Collaborator

This is a GREAT feature to add! Thank you! I've got a couple things I may follow up on, but in the meantime will pull this down and run it through a couple test apps I have locally.

@kerrizor kerrizor merged commit 2071305 into voormedia:master Aug 10, 2016
@kerrizor kerrizor added this to the 1.4.8 milestone Aug 10, 2016
kerrizor added a commit that referenced this pull request Aug 10, 2016
Lots of new stuff in 1.5.0! We've gotten Rails 5.x support in place, as
well as adding 2 new options. "clustering" will draw a box around models
contained in the same name space, helping to visually organize areas of
concern. "only_models_include_depth" - although awkwardly named - will
restrict the depth of graphing to the supplied value.

* New option of 'clustering' by namespace (#205)
* Support for 'only_models_include_depth' option (#219)
* Added basic support for non-Rails apps (#208)
* Avoid duplicate specializations when using STI with an abstract base class (#211)
* Fixed Ruby 2.1 deprecation warnings (#209)
* Fixes to tests (#210, #213)
* Various documentation fixes (#203, #212)
@kerrizor kerrizor mentioned this pull request Aug 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants