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
If user moves between different object types form submission, you can see that the load times for forms are taking longer. This affects checking form status and can give false positives on isDirty. Might also be related to "clear form" action which doesn't seem to work right.
To Reproduce
Steps to reproduce the behaviour:
Go to WizardFillObjectDetailsForm component
In FormContent method log formschema
Move between forms on different object types
Console logs form schema multiple times
Expected behavior
Form should be rendered only once when object type changes.
The text was updated successfully, but these errors were encountered:
It seems that if user navigates to xml upload between different object type form, resolver is fired only once. This might be fixed with nulling form data between object type change.
Fixed with destroying form component between changing object types. Form component is given a key (a random number at this point, should be more convenient). Component is destroyed when the key changes and therefore doesn't do unnecessary validations. This is going to be fixed when bugfix/prevent-draft-version-alert-popping-incorrectly is merged.
This improves performance by lot. Fixed form reset also.
Describe the bug
If user moves between different object types form submission, you can see that the load times for forms are taking longer. This affects checking form status and can give false positives on isDirty. Might also be related to "clear form" action which doesn't seem to work right.
To Reproduce
Steps to reproduce the behaviour:
Expected behavior
Form should be rendered only once when object type changes.
The text was updated successfully, but these errors were encountered: