fix: persist values after validation errors on tags fields that acts as taggable on #2868
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
|
Code Climate has analyzed commit 59b9d99 and detected 0 issues on this pull request. View more on Code Climate. |
gabrielgiroe1
approved these changes
Jun 18, 2024
|
This PR has been merged into Please check the release guide for more information. |
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.
Description
Fixes #2724
Acts as taggable on stores the tags values through DB tables. When the record is not DB persistent (on a new unsaved record) the tags values only can be accessed directly from the record's tag list.
tag_list_on(acts_as_taggable_on_option)helper does the trick.Checklist:
Screenshots & recording
acts_as_taggable_on_fix.webm