chore: fix type definition for unbindElement#4425
Open
wridgeu wants to merge 1 commit intoUI5:masterfrom
Open
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
1 participant
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.
unbindElementis missing the proper JSDoc for declaring it as optional making it a bit cumbersome to use in TypeScript.The internals behind it (the original impl. of ManagedObject), already has this properly marked as optional.
I did not want to also adjust/align the JSDoc descriptions writing style (that'd just be nitting the style). I also did not verify 'all' other JSDocs. This particular one was just one I stumbled over during work.
When this change lands on new npm types packages, it'll help people using TypeScript.