You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a page for the configuration of routes to the project. This page will be used to edit the details of existing routes in the config.yml file of the backend. We thought of two ways for implementing this in the frontend-
Having a single page with something like a text editor where the user can directly edit the config file.
Pros: It will be less burdensome for the user if he wants to change multiple routes at once.
Cons: The user might feel absurd on suddenly seeing an entirely new page without the sidebar.
Having an option to switch between the graph and the config page of an individual route.
Pros: This will have a better UI, and the user can seamlessly use the same sidebar that he was using for getting the graphs of routes, even to edit the routes.
Cons: This might lead to unnecessary complications in the frontend code.
Note: The proposed design for the second approach could be found here
The text was updated successfully, but these errors were encountered:
Add a page for the configuration of routes to the project. This page will be used to edit the details of existing routes in the config.yml file of the backend. We thought of two ways for implementing this in the frontend-
The text was updated successfully, but these errors were encountered: