Fixing Issue 1911#1922
Merged
joaojmendes merged 1 commit intopnp:devfrom Dec 12, 2024
Merged
Conversation
Collaborator
|
Hi, @NishkalankBezawada. Thank you for the fix. |
Contributor
Author
Hey @joaojmendes João, This was very quick. Thanks for reviewing this, |
Merged
This file contains hidden or 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
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.
What's in this Pull Request?
This PR fixes
Problem
When adding a new term using ModernTaxonomyPicker, the newly added term is adding to the parent directly. Instead it should be added as a child to its parent as below.
If the panel is refreshed, the newly added term is properly set unders its parent.
Observation
The method
updateTaxonomyTreeViewWithNewTermItemsin theTaxonomyTreecomponent is called while adding new terms fromModernTaxonomyPickercontrol, in which by default, the level of the term where it should be added is set to be the main group, instead, it should be to the parent term.Solution
Added a new property as
parentTermwhich is only used while adding new terms.And
As below,
With this change, the newly added terms are adhering to the flow, to add as a child term to the parent (Selected term) as below.
Thanks,
Nish