Open marthakeezy opened 3 weeks ago
Given the low likelihood, and low impact, agree severity is low, but we should be using our LoadingButton
component on any actions that might take time, so the button is disabled while the prescription is being created 👀 If LoadingButton
is being used, we need to check if the correct loading state is being passed in?
Moving priority to normal because of the solution proposed by Lache about loading state
What went wrong? 😲
A little hard to recreate! I've seen it twice, and they occurred when there was an action (e.g. adding a new item to a prescription), and the system was a bit slow to update, causing the screen to freeze, and when I clicked the
Save
button again to try and save the changes, the error showed upHard to run into, so marking as
Low Severity
Expected behaviour 🤔
Error should not be there
How to Reproduce 🔨
Steps to reproduce the behaviour:
OK
multiple times in quick successionYour environment 🌱