-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat(heureka): optimizes performance - separates total count and page info from main data #450
Conversation
🦋 Changeset detectedLatest commit: 44a26c1 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Little comment from my side
apps/heureka/src/components/issueMatches/IssueMatchesDetails.jsx
Outdated
Show resolved
Hide resolved
I try to search by regular expression, but it seems not to work. |
The search in the Heureka API is based on wildcard search, which is simpler but more limited than regular expressions. Therefore, I believe it does not fully support regular expression syntax. |
ok, but the placeholder is "Search term or regular expression" :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Summary
Optimized the data fetching for main views in Heureka to improve performance with large datasets (millions of issues). This change splits the fetch requests for all three views (IssueMatches, Services, and Components) by separating the total count and page info queries from the main data queries.
Changes Made
Some small fixes:
Related Issues
Screenshots (if applicable)
Testing Instructions
npm i
npm run TASK
Checklist