MVJ-394 MVJ-UI refactor area search into hook syntax #509
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
NC-jsAhonen
force-pushed
the
MVJ-394-mvj-ui-refactor-areaSearch
branch
3 times, most recently
from
acadf56 to
3a14750
Compare
NC-jsAhonen
force-pushed
the
MVJ-394-mvj-ui-refactor-areaSearch
branch
from
3a14750 to
f4e45a5
Compare
|
@NC-jsAhonen Is this now ready for review? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These changes migrate the code from the older and less documented class syntax into the current standard React practice of hooks.
ATTENTION
There was a previously existing bug that is unrelated to this change: the attachments are not rendered immediately after they are added to area search application forms, and the UI gets stuck after doing so.