LiteSun opened a new issue #1588: URL: https://github.com/apache/apisix-dashboard/issues/1588
## The current front-end approach To create a route for example, the front-end will be regular [1] check for certain fields, such as name field, if the regular condition is not met, the front-end page will report an error and block the user's next operation.  ## The disadvantages of the current approach The current front-end can meet the verification requirements. However, when the back-end changes the verification rules, the front-end has to passively and manually update the verification rules for the corresponding fields. If the back-end does not notify the front-end in time or misses some fields, then the synchronization of the front-end and back-end verification will be a problem, affecting the user's use. ## Improvement measures After communicating with @membphis , using jsonschema validation would be a good choice. The front-end calls the API to get the jsonschema of the corresponding module and then maps the corresponding jsonschema rules to the corresponding field checks on the front-end. Do this when the back-end update the validation rules, the front-end can automatically synchronize the latest validation rules, reducing unnecessary development time of the front-end. [1] regular expressions provided by the back-end, and then manually added by the front-end developers to the corresponding form form for the field validation cc @juzhiyuan @liuxiran @guoqqqi ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
