Skip to content

Introduce a specification for "custom" behaviour #9

@whitfin

Description

@whitfin

In one of our internal implementations, we use a $geo operator. This is very specific and should not be part of the actual specification.

Instead, we should leave space in the specification for custom operators (that a backend can implement and document alone), and just enforce the format of the operators in general.

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