Skip to content

Query Hooks Improvements - #5681

Draft
bjoernricks wants to merge 23 commits into
mainfrom
query-hooks-improvements
Draft

bjoernricks wants to merge 23 commits into
mainfrom
query-hooks-improvements

Conversation

@bjoernricks

@bjoernricks bjoernricks commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

What

Query Hooks Improvements

Extend and improve the query hooks to make them consistent.

Why

We should have one dedicated API for querying data. This means we should get rid of

  • The redux store completely
  • Using the GMP API in interface components

Checklist

  • I have added tests for the changes
  • I have used the following LLMs/AI tools in this pull request:

Use dedicated modules for single and multiple entity query hooks.
Use dedicated modules for single and multiple entity query hooks.
Ensure when cloning and deleting tickets via their query hooks a
notification message is displayed.
Use dedicated describe blocks for each hook and use real model instances
in the tests.
Ensure when cloning and deleting users via their query hooks a
notification message is displayed.
Allow to query Target data via use query hooks.
As query hooks might not return a response object and instead the data
directly the goToDetails function needs to support this use case.
Refactor TargetComponent to use the new query hooks for target.
Before the changed port list was re-loaded after a port range was
deleted. This is completely unnecessary and also created several
additional requests when a user deleted several port ranges in the
dialog.
Allow to query and mutate port lists via query hooks.
Use the new port list query hooks within the PortListComponent.
Implement the basic set of query hooks for credentials.
Update TargetComponent and TargetDialog to use the new port list and
credential query hooks internally instead of directly querying the gmp
API.
@github-actions

github-actions Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Snapshot Warnings

⚠️: No snapshots were found for the head SHA cfe5a3d.
Ensure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice.

Scanned Files

None

Entity and entities queries are separated everywhere else already.
For deleting a user an additional input argument is required.
…ssage

Ensure that the name argument is passed by default and the type checker
complains about it. This ensure the success message is displayed
correctly.
Use useDeleteMutation and adapt arguments to recent changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant