Skip to content

Change search pattern across the applicationΒ #2239

@jonodrew

Description

@jonodrew

Proposal

We should switch to a more traditional search pattern, where a user fills in a search form, the application queries the database, and returns a small set of results for the user to then take action against. For example, when directly adding people to a workshop, the admin would type a name into a search bar. They click 'search' and receive a list (or possibly just one) result. They click on the result and then take action.

Why this?

The application was originally built without realising how massive our chapters would get. As a result, we load hundreds of Member records into the frontend, and then filter them using javascript. This slows the application down and makes it really difficult to use for admins.

Why now?

We've got a small team set up around maintenance, and this would be a significant quality of life improvement.

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