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

Impact not updated when quick presets are updated #2014

Closed
holtgrewe opened this issue Oct 10, 2024 · 4 comments · Fixed by #2027
Closed

Impact not updated when quick presets are updated #2014

holtgrewe opened this issue Oct 10, 2024 · 4 comments · Fixed by #2027
Assignees
Labels
bug Something isn't working

Comments

@holtgrewe
Copy link
Collaborator

Describe the bug
For a particular case (details in internal chat), impact is not adjusted when quick presets are changed.

To Reproduce
See internal channel.

Expected behavior
Impact should be changed.

Additional context
N/A

@holtgrewe holtgrewe added the bug Something isn't working label Oct 10, 2024
@holtgrewe holtgrewe assigned holtgrewe and stolpeo and unassigned holtgrewe Oct 10, 2024
@holtgrewe
Copy link
Collaborator Author

holtgrewe commented Oct 10, 2024

@stolpeo can you do a RCA?

@stolpeo
Copy link
Contributor

stolpeo commented Oct 11, 2024

RCA

If a quick preset exists that has not set a value for at least one of the settings and this quick preset is selected, the javascript throws an error and creates an inconsistent state that causes all subsequent quick preset selections to fail. The line that is causing this is located here:

for (const [key, value] of Object.entries(

@stolpeo
Copy link
Contributor

stolpeo commented Oct 11, 2024

Solution

  1. This kind of error should be caught in that function
  2. We enforce that all settings in a quick presets must be set

@stolpeo
Copy link
Contributor

stolpeo commented Oct 11, 2024

RCA 2

There is another error that only displays the preset sets in the editor once a case from the project was loaded. It fails if you go directly to the editor (when reloading the page for example) because the caseListStore is only initialized when a case was loaded. Fix is easy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants