kislayverma / rulette-server Goto Github PK

A user should be able to select a rule system provider and trigger a refresh of all rule systems under it. This will be useful where a rule system is added under a provider and we want to refresh the UI/API to access it.

Built on top of kislayverma/Rulette#75, this will allow us to load all rule systems exported by a provider instead of loading only those which are given in the application config given at startup

This is good because now teams exposing rule systems can simply add rule system and they will start showing up instead of having to update the application config and restart servers

A call to get the rule for an input returns the full rule object, which is both un-necessary and revealing in too much internal implementation details.

We should return a more pared down object, which contains only the rule fields and the output value

The current API will try to return all the rules in one go. If there are lots of rules, this might cause the API to take a lot of time to respond. There should be an option to get rules in a paginated manner

We should create a REST API layer on top of kislayverma/Rulette#71

User should be asked for a confirmation on clicking the delete rule button before the delete is executed.

Ref link for doing this - https://stackoverflow.com/questions/23775272/bootstrap-modal-before-form-submit

The current API will try to return metadata of all rule sstems in one go. If there are lots of rule systems, this might cause the API to take a lot of time to respond. There should be an option to get metadata records in a paginated manner

• Make the scheme uniform
• Use semantic URLs as far as possible

We should have a UI which performs live evaluiation of inputs that the users enters in it and returns the applicable rule

We should be able to run multiple instances on rulette-server as a cluster with data changes replicating seamlessly across all instances.

We can add a button to allow reload of rule system the UI