Add ability to use errorTemplate on the field level as well + ability to differentiate between where the physical error is placed #71
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
added 4 commits
August 31, 2015 12:49
…ed and where the CSS class is added using errorLocation. If it's not set, errorLocation = errorTarget.
… is placed and where the CSS class is added using errorLocation. If it's not set, errorLocation = errorTarget." This reverts commit 6b25c26.
beerendlauwers
changed the title
|
See @8f19781 and @56fc5b0 for the code changes, the other two commits are flukes. Sorry about that. |
|
Sorry this has been sitting for so long, i'm seeking new maintainers, let me know here if you're interested: #72 |
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.
I needed to be able to customize the layout of the errors on a per-field basis. Here are the code changes.