feat(rich-text-links): improve getRichTextEntityLinks() #738
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.
WHAT?
Improve the implementation of
getRichTextEntityLinks()
so that instead of receiving atype?: string
, it receives...type: (BLOCKS | INLINES | string)[]
.WHY?
When specifying the
type
parameter. Most often than not, there's a need to filter on more than onetype
. Before this change, users were forced to callgetRichTextEntityLinks()
for each type. By accepting multiple values, a single invocation can get all the desired output more efficiently.As for the
BLOCKS | INLINES
in addition tostring
, it's merely used for documentation reminding library users that they can specify the values in there, rather than explicit string values.HOW?
yarn build && yarn test && yarn lint && yarn prettier:check