Skip to content

Seeking guidance on standard #395

Closed
Closed

Description

@dgreene1

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

  1. abbasc52 commented on Oct 3, 2022

    @abbasc52

    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

  2. YogeshPraj commented on Oct 14, 2022

    @YogeshPraj
    Contributor

    Most widely use format to configure rules from UI.

    image

    This requires simple json structure to store values from UI.
    image

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

  3. locked and limited conversation to collaborators on Oct 26, 2022
  4. converted this issue into a discussion #415 on Oct 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions