swagger-api/swagger-codegen

Client-generation: Allow data validation on the client side (using minLength/maxLength)

Open

#2,549 opened on Apr 11, 2016

View on GitHub
 (36 comments) (0 reactions) (0 assignees)HTML (5,474 forks)batch import
Client: JavaEnhancement: Featurehelp wanted

Repository metrics

Stars
 (12,701 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Currently the generated Java-clients perform required-validation automatically. Do you think this makes sense for minLength/maxLength as well, to reject the request on the client side before sending to the server?

For Java the JSR-303 Bean Validation API could be used for this automatically. For other languages maybe a JSON-schema validation could be used.

Contributor guide

Research direction
Investigate where client side validation logic is implemented in the code generator templates and how to add minLength/maxLength constraints using JSR 303 annotations or JSON schema validation.
Tech stack
java
Domain
api
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65