Fix regression where selected parent node is not passed to addEdit location form #1273
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
peterMuriuki
requested review from
machariamuguku,
kahummer,
KipSigei and
JohnMwashuma
peterMuriuki
force-pushed
the
fix-set-parent-id
branch
from
d8758ea to
2c4dc58
Compare
kelvin-muchiri
approved these changes
Nov 10, 2023
6 tasks
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.
On the locations page, selecting a node and then clicking the add location unit, should default to using that location as the intended parent node in the add edit location view. There seems to have been a regression where this was no longer the case in recent releases.
This pr fixes this behavior and correctly identifies the selected node as the default parent node in the location form.