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
Can you share with me if there is a universally agreed upon standard for sending rules over HTTP via JSON?
Because I notice that there is a schemaa schema in the repo but it doesn’t appear to be a standard— it’s just what this library uses.
So what I’m looking for is a JSON Schema spec that I can point to to say “this is what the API that reads the rule selections expects to receive.”
For full context, my team is building a rule builder UI and unsure of what engine we’ll be using. So having a standardized output will allow us to make that swap easily (ie the adapter pattern). And it will let us start building the UI before the engine has been decided upon. Thank you for the guidance.
Side note: I find this library to be wonderful but I have concerns about the expression part of the schema since it seems unclear what would constitute a valid string. Like is it any JS?
Activity
abbasc52 commentedon Oct 3, 2022
Hi Dan Greene (@dgreene1), currently there is no universally agreed upon standard.
On your second question, the expression used in RulesEngine is C# expression . You can find more details here - https://microsoft.github.io/RulesEngine/#c-expression-support
YogeshPraj commentedon Oct 14, 2022
Most widely use format to configure rules from UI.
This requires simple json structure to store values from UI.

Backend can use this format to translate to respective BRE engine format using adapter pattern (e.g, MicrosoftBRETranslatorPlugin).