Fix for refinement#include deprecation warning #208
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
Fix refinement#include deprecation warning as I mentioned on palkan#207
GoktugOzturk
changed the title
|
There is no need for test or documentation updates. Added line for changelog. Also since Ruby 2,6 is EOL, maybe you can remove it from unittests. Seems like that is the only version that fails. |
|
Also, can we release 0.6.1 so we can start using this without a field revision number? |
added link for issue number
palkan
pushed a commit
that referenced
this pull request
May 24, 2022
Done! |
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.
fixes #207 refinement#include deprecation warning
PR checklist: