Repository navigation
Migration tools: Fix vocabulary terms handling - #202
Merged
Merged
Conversation
I feel very paranoid about why I suddenly had to address this after years of it not being an issue. But suddenly everything was broken and this was the fix after refcache was moved to Gemfile from gemspec.
- is more lenient with format of opt_fields capitalization and autocorrects errors in this - more tolerant handling of "errors" that don't really matter. We can just skip creating a record that already exists if it doesn't need to be updated. We don't need to yell about it. It ain't that serious. - streamline updating term records that were sent as adds, since we already have the existing record's term info
This file contains hidden or 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
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.
No description provided.