Design the settings screen

[Harkishen-Singh]

The settings screen contains parts of config file which comes under the props required for running BR effectively. These must be shown interactively in the UI, along with the ability to change or update the values.

At present, the local-config.yml contains the following fields:

1. password
2. test_interval
3. service-states
4. response-length
5. routes

Since, we aim to use the config file as a local-db as well, obviously, some part of this would be editable and the rest uneditable.

Editables

1. password
2. test_interval
3. routes

Un-editables

1. service-states
2. response-length

Hence, the settings screen would contain the following which can be editable:

1. password
2. test_interval

The dashboard would contain:

1. service states
2. response-length of individual routes

We will have a routes screen, named as configure routes (or any relateable name) which would be responsible for CRUD operations involving routes. This should be done dynamically just like that in postman.

[ankitjena]

I would like to work on this. We can make a editable form or just a form for the settings. What do you suggest?

[Harkishen-Singh]

@ankitjena some part of the config.yml needs to be updateable. We will make only those things editable.

In fact, the settings have to be divided into two parts:

1. Contains the configuration information like interval editable, password editable, service-state uneditable, many others... (needs proper categorisation)
2. For adding more routes. This would be the routes screen where the CRUD operation on the routes would be done.

[Harkishen-Singh]

@dikshantbrahma @ganeshpatro321 please look into this module. Also, please have a plan on the above said.

[Harkishen-Singh]

@ankitjena @dikshantbrahma @ganeshpatro321 I have updated the issue according to the discussion. Please have a look if it sounds satisfying.