investigate supporting --client-side-validation
See original GitHub issueOther languages support this flag
Whether you want the SDK to perform validation on inputs and outputs, based on swagger information. Recommended to be
false
for track 2 code, since we want the network to validate instead. Defaults tofalse
.
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Client-side form validation - Learn web development | MDN
This is called client-side form validation, and helps ensure data submitted matches the requirements set forth in the various form controls.
Read more >Client-Side Form Validation with HTML5 - SitePoint
A look at some of the easy to use form features in HTML5, to help you validate user-entered data before it reaches the...
Read more >HTML 5 client side validations - ADG
HTML 5 client side validations are a very useful feature: they allow rudimentary validation of user data without submitting anything to the ...
Read more >Side Validation - an overview | ScienceDirect Topics
Although this example illustrates the server-side validation, ASP.NET automatically writes client-side code to perform the validation. There are various options ...
Read more >Add client side validation for Bootstrap IFE support - Drupal
Add option to turn client side validation on and off. We don't like how browsers handles client side validation (different visual ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@sarangan12 Please check back with the autorest feature crew about this. Do we have cases where this flag was useful? From what I recall the recommendation was always to avoid client side validation and expect the service to throw proper errors for wrong input
@deyaaeldeen My vote is yes. We are translating everything that is provided in the swagger. So, we could continue the same. However, we have made a org decision that we will not act upon it i.e. not validate it. I am open to alternative viewpoints too