pnp / pnp/sp-dev-fx-controls-react

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

Open
#1,911 1 comment 0 reactions 1 assignee View on GitHub

@NishkalankBezawada is already working on this.

Since Dec 11, 2024.

status:fixed-next-drop type:bug
Dominant language
TypeScript
Stars
433
Forks
418
Avg merge
5d 6m
Merged PRs (30d)
19

Description

[ ] 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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.