TaxonomyPicker control allows select deprecated/untaggable terms when typing

[kallejar]

Thank you for reporting an issue, suggesting an enhancement, or asking a question. We appreciate your feedback - to help the team understand your
needs please complete the below template to ensure we have the details to help. Thanks!

Please check out the documentation to see if your question is already addressed there. This will help us ensure our documentation is up to date.

Category

[ ] Enhancement

[ x] Bug

[ ] Question

Version

Please specify what version of the library you are using: [ 3.5.0 ]

Expected / Desired Behavior / Question

We have in our term set deprecated and untaggable terms set. On the control I have both these options true.
hideTagsNotAvailableForTagging={true} hideDeprecatedTags={true}

The true value works when you pick the terms via the tag-icon

But if you type directly to the control field you are able to find and pick the term


Console.log

I would expect both typing and selecting term via picker would work the same when using those control propeties

Observed Behavior

If you are reporting an issue please describe the behavior you expected to occur when performing the action. If you are making a
suggestion or asking a question delete this section.

Steps to Reproduce

I have following configuration for the control:
<TaxonomyPicker allowMultipleSelections={false} termsetNameOrID={this.props.webPartProperties.termSets.reportType.guid} panelTitle={strings.newReportTypeLabel} placeholder={strings.newReportTypeDescription} label={strings.newReportTypeLabel} context={this.props.context} onChange={this._onTaxPickerChangeReportTypeProxy} isTermSetSelectable={false} required={true} hideDeprecatedTags={true} hideTagsNotAvailableForTagging={true} />

There seems to have been similar issues in past
#506
#109

[ghost]

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[github-actions]

Thank you for submitting your first issue to this project.

[manipk]

Also request this issue to be resolved. Can we know the status on this bug

[ekapic]

Hi there!
I've fixed this issue in PR #1354

[joelfmrodrigues]

@kallejar many thanks for reporting the issue.
The PR from @ekapic has now been merged and the fix will be in the beta release shortly. Will also be included in the next main release.