This repository was archived by the owner on Jan 7, 2021. It is now read-only.
Remove 'invalid' translation from locale specification #3
Conversation
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
- And update documentation
Owner
|
Thank you for your contribution. Development was moved to https://github.com/state-machines |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Did this in order to avoid overriding user settings for errors.attributes.[name].invalid and errors.messages.invalid as these have a lower priority. Plus, "invalid" already has a default setting (although I don't know how many years ago this made it into the default locale settings).
This is a port of a PR opened by @adimichele that's been hanging out on the original state_machine repo: pluginaweek#200