Upgrade virtus to version 2.0.0 #55
Open
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.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ virtus (~> 1.0 → ~> 2.0) · Repo · Changelog
Release Notes
2.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 42 commits:
Update ChangelogReplace Equalizer with Virtus::EqualizerUpdate ChangelogBump virtus to 2.0.0Add simplecovUpdate CC reporting on travisRun CC coverage under 3.0Remove deps that are not critical to run the test suiteRe-add 2.0 to travis and set >= 2.0 as min in gemspecUpdate READMEOK now I'm just curious if this will pass :DRemove ancient rubies from travisUpdate ChangelogPort to use dry-inflectorRemove ruby-version fileDISCONTINUEDMerge pull request #375 from syguer/add_ruby_versions_for_specCI against ruby 2.3 and 2.4Add info about dry-rb gems to the README [ci skip]Travis-CI will install Gems for us, let them deal with that.Double our build speed on Travis-CI.Drop `bundle exec rake spec'Use Travis-CI addons for CodeClimate.README: Show correct result for `user.attributes`Merge pull request #343 from dslh/collection_value_coerced+ Virtus::Attribute::Collection.value_coerced?Merge pull request #312 from aarondcohen/patch-1Merge pull request #285 from nunommc/masterMerge pull request #345 from smanolloff/masteradd virtus-relations extension in README.mdMerge pull request #338 from XescuGC/pluginsAdded to the README the plugins/extensionsMerge pull request #333 from novikserg/fix_failing_specsChange behavior of Attribute#== methodUse Virtus::Equalizer instead of Equalizer gem in Virtus#Attribute (behavior preserved)Add specs for attributes comparison (based on latest Equalizer gem working version)Merge pull request #326 from novikserg/325_mass_assignment_bug_fixAdd tests for "attributes" attributeRevert "Include allowed_writer_methods only when mass-assignment is turned on"Update README.mdMerge pull request #317 from jdongelmans/fix-attribute-documentation-typoFix a small typo in documentationDepfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands