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.

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

🐛 Refresh affect trackers after filing trackers #472

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

superbuggy
Copy link
Collaborator

[OSIDB-ID] [Title]

Checklist:

  • Commits consolidated
  • Changelog updated
  • Test cases added/updated
  • Jira ticket updated

Summary:

[Replace with a brief summary of the changes introduced by this PR.]

Changes:

[Replace with a detailed description of the changes made in this PR, including any new features, enhancements, bug fixes, or refactorings.]

Considerations:

[Replace with any additional considerations, notes, or instructions for reviewers.]

Closes OSIDB-3483

@superbuggy superbuggy requested review from C-Valen and a team November 1, 2024 16:21
@superbuggy superbuggy self-assigned this Nov 4, 2024
@@ -239,3 +240,15 @@ function flawErrors(flaw: ZodFlawType) {

return mirroredFlaw;
}

export async function refreshFlawAffectTrackers(flaw: Ref<ZodFlawType>) {
const freshFlaw = await getFlaw(flaw.value.uuid);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we add some kind of loader to this action?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, now that the trackers are handled asynchronous, I'm not sure about UX, we are realoading things but it may occur that nothing changes, users are already aware of that, but it can be confusing

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hrm, maybe we should the delay should be long just to grab the flaw, but that might be best to trigger a loading state

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.

2 participants