Skip to content

Seeking guidance on standard #395

@dgreene1

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?

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