-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Location Search and Subject Search inputs are not debounced #1215
Comments
himeshr
added a commit
that referenced
this issue
May 16, 2024
himeshr
added a commit
that referenced
this issue
May 16, 2024
himeshr
added a commit
that referenced
this issue
May 16, 2024
himeshr
added a commit
that referenced
this issue
May 16, 2024
Impact AreasDEA
App Designer
|
himeshr
added a commit
that referenced
this issue
Jun 4, 2024
petmongrels
pushed a commit
that referenced
this issue
Jun 10, 2024
petmongrels
pushed a commit
that referenced
this issue
Jun 10, 2024
petmongrels
pushed a commit
that referenced
this issue
Jun 10, 2024
petmongrels
pushed a commit
that referenced
this issue
Jun 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
In DEA, while searching for a Subject or, while create/editing an Individual, for LocationFormElements and SubjectFormElement, we do not debounce the input, and end up invoking a costly search api on the server.
This also leads to poor user experience. We should atleast mitigate server side impact.
To Reproduce
Steps to reproduce the behavior:
Case 1:
Case 2:
Similar behaviour while searching for Subject using SubjectFormElement.
Expected behavior
We debounce the search and select (location / Subject) calls in DEA.
Developer Checklist(Developer fixing the bug should fill this checklist)
Impact Areas
The text was updated successfully, but these errors were encountered: