Open
Conversation
Updated the date for the validation documentation and clarified the remote validation section.
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
1 participant
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.
Fixes #33239
Tom ... Looking at the items on the issue](#33239) ...
Not a problem any longer. The article section was updated at some point and no longer makes it seem like jQuery is required for CreditCardAttribute, which does its own calcs for the Luhn algorithm.
I think we can just cross-link the Blazor Forms node landing page. It's something that I hope a dev working with Blazor will find when they're looking at the Blazor node.
I still think that passage can be improved. I make a suggestion on this PR for how that text might compose.
Internal previews