-
Notifications
You must be signed in to change notification settings - Fork 542
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support to show raw data for Route, Upstream, Service and so on #1399
Comments
This feature allows the user to see the data faster and more intuitively, a very good feature. It is necessary to check the legitimacy of the data if the user is allowed to enter it manually. otherwise, such a problem #1234 will occur. |
This feature would be more practical for advanced users, Perhaps As we have plan to deprecate the |
Long term support, of course, both |
Solutions design:On the page, in the list of route, service, consumer and upstream, add a view button. When the user clicks view, a Drawer will pop up on the right side, and the corresponding data will be displayed in the form of json in the Drawer. The code editor uses codemirror, the same as the plugin editor;
Discussion needed:If the user uses raw data for editing, the edited data is missing fields that the front-end depends on, which can cause the page to crash. Can we use jsonchema to verify that the data entered by the user is legitimate, just like we verify that the plugin is legitimate? |
As far as I know, the backend is using this method to check the client's input, right? |
ping @LiteSun |
|
@LiteSun |
ok, let me do more research on how to prevent the page from crashing if a field is missing. |
Feature request
Please describe your feature
Due to some fields are not supported by Frontend, once users modify a Route that is created by admin API, then that Route would be overridden by Frontend's data.
Describe the solution you'd like
We may first support showing raw data and allow the user to modify it directly and add some tips before submitting data change, to tell the user to be careful if this Route is created by Admin API.
If possible, we could support Data Diff before data submitting.
cc @LiteSun @liuxiran @membphis
The text was updated successfully, but these errors were encountered: