[Form] Documented legacy_error_messages #14577
Merged
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
| Timo, thanks a lot for this amazing pull request! I can only imagine the effort that you put here to carefully update all error messages. Moreover, because of the cumbersome syntax of RST tables, which makes it difficult to rearrange contents. That's why we appreciate a lot the work you did here. Again, thanks for your tremendous work in this PR 🙇 |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
Documented new legacy_error_messages option for forms and documented all new default and legacy
invalid_messagevalues for each form type.Also moved/added
invalid_messageas overridden option in all applicable form types.Fixes #13954