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

support for 'only_models_include_depth' option #219

Merged
merged 2 commits into from
Aug 10, 2016
Merged

support for 'only_models_include_depth' option #219

merged 2 commits into from
Aug 10, 2016

Conversation

kerrizor
Copy link
Collaborator

Fixing up work done by @durandom in #189 preparing for a release.

durandom and others added 2 commits May 12, 2016 15:04
walks relationships and recurses them to a defined depth.
e.g. only_recursion_depth=2 includes associations up to 2 levels deep
@kerrizor kerrizor added this to the 1.4.8 milestone Aug 10, 2016
@kerrizor kerrizor merged commit a75d23c into master Aug 10, 2016
@kerrizor kerrizor deleted the pr-189 branch August 10, 2016 19:58
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
@durandom
Copy link
Contributor

thanks @kerrizor ❤️

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

Successfully merging this pull request may close these issues.

None yet

2 participants