Mention Rails 5 in README #212
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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)
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After many years I've used this gem with a Rails 5 project, and it works just fine! Except for some minor issues for which I've opened pull requests.
Thanks @kerrizor for your awesome working maintaining this gem!