Skip to content

Revisit query/restriction mechanism #61

@guzman-raphael

Description

@guzman-raphael

We should revisit the restriction mechanism to provide increased flexibility and simply its use.

Perhaps we might want to look into Lecene query syntax (same as used by GitHub). Taking a closer look at their GH API and combining into our requirements, it could look something like this.

query params

page=2
per_page=3
order=asc:student_id desc:student_enroll_date
q=-student_major:engineering OR student_enroll_date:[1612063661 TO 1613063661]

Just would need to be sure to encode properly using encodeURIComponent('-student:engineering ...')

Best to defer rework on this as not on critical path to upcoming milestones.

Also see this tutorial.

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