Add deprecation for @dropdownId (undocumented & not handled correctly)
#1012
Conversation
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.
Many years ago, there were two arguments:
@triggerIdand@dropdownId.It seems we never removed
@dropdownId, even though@triggerIdwas removed years ago.Passing
@dropdownIdonly works when a custom trigger is implemented, which means it can cause issues in normal use cases. For this reason, it is now deprecated and will be removed in the next major release.Note: This property is also undocumented.
Users who have passed this parameter will now receive a deprecation warning and should switch to using
publicApi.uniqueIdinstead.Close #673