Skip to content
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.

Sign up for GitHub

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

Update DG #358

Merged
merged 1 commit into from
Apr 15, 2024
Merged

Update DG #358

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions docs/DeveloperGuide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1958,3 +1958,16 @@ Currently, the application only supports a few pre-defined relationships with fi
* Use an external library or dictionary to define a set of valid roles for each relationType.
* Ensure that the roles provided by the user match the valid roles for that relationType.
* Display an error message to the user if the roles are not appropriate for the relationType.


### C.9 - Improve UI handling of filtering commands

Currently, when the user uses a filtering command e.g. `find`, `anysearch` and `familysearch` the subsequent results will remain filtered and other commands will not act as expected.

* Proposed Enhancement:
* Improve the backend handling of filtering commands by automatically clearing the filter after each successful call of the filtering functions.

* Implementation Details:
* Update the list component after every successful `find`, `anysearch` and `familysearch` commands to automatically clear the filter after displaying the results.
* Ensure that the filter is cleared when the user executes a new command or closes the application.
* Display a confirmation message to the user indicating that the filter has been cleared.
Loading