Skip to content
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

[ModernTaxonomyPicker] - Adding a new term adds the term to the parent level, but not to the child level. #1911

Open
NishkalankBezawada opened this issue Nov 27, 2024 · 0 comments

Comments

@NishkalankBezawada
Copy link
Contributor

[ ] Enhancement

[x] Bug

[ ] Question

Version

Please specify what version of the library you are using: [ v3.19.0 & In dev branch as well]

If you are not using the latest release, please update and see if the issue is resolved before submitting an issue.

Expected / Desired Behavior / Question

While adding a new term using ModernTaxonomy Picker, the newly added term should be added as a child to its parent.

Observed Behavior

While adding a new term using ModernTaxonomy Picker, the newly added term is adding to the parent level as below.

Untitled+video+(16)

If the panel is refreshed, the newly added term is properly set unders its parent.

Steps to Reproduce

I was implementing Adding new terms in ModernTaxonomyPicker control for a client as below, using the advanced example as mentioned in the documentation

image

where updateTaxonomyTreeViewCallback implements to refresh the panel with the newly created term.
The newly created term is created, and shows at the parent level which it should not.

Note

I will be happy to send in the PR for this, as the client needs this functionality.

Thanks!
Nishkalank

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant