-
Notifications
You must be signed in to change notification settings - Fork 2
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
bug/wg-447-import-loading-bug #334
Conversation
useEffect(() => { | ||
setIsSuccess(false); | ||
}, [selectedFeature.id]); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would this not work with the isSuccess
value from the mutation instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not as it is no. The isSuccess key is the selected project feature list not the specific feature. Adding the feature id as an additional key won't update the list in the LoadedProject component. The loaded map project is looking for the feature id to change and since the import doesn't change an id, we are invalidating the key list features on import. The trickle down of selectedfeature state from loadedmapproject could possibly use some refactoring based on these conflicts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works as-is. Just a suggested change to use the built in mutation method
Co-authored-by: Sal Tijerina <[email protected]>
Overview:
PR Status:
Related Jira tickets:
Summary of Changes:
Testing Steps:
UI Photos:
Notes: