You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whether or not the current method of deciding if the current parameter set selected by the user is slowing down the app considerably, it is certainly using a lot of resources. Not something that I want to be true about this app.
Possible Solution
instead of calling the generator after every change to state, we could call it only when the user clicks the button, and if their parameters would result in an empty list, then we can render the error message and disable the button until the parameter list changes (maybe a reactive variable looking at the current state of the readSpellParameters store?)
The text was updated successfully, but these errors were encountered:
Whether or not the current method of deciding if the current parameter set selected by the user is slowing down the app considerably, it is certainly using a lot of resources. Not something that I want to be true about this app.
Possible Solution
instead of calling the generator after every change to state, we could call it only when the user clicks the button, and if their parameters would result in an empty list, then we can render the error message and disable the button until the parameter list changes (maybe a reactive variable looking at the current state of the
readSpellParameters
store?)The text was updated successfully, but these errors were encountered: