Render availability items without version range details #891
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.
Bug/issue #, if applicable: 135420580
Summary
This makes the
AvailabilityRange.introducedAt
prop optional instead of required.This adds support for indicating that a symbol is available on a certain platform, even if there are no additional details on the specific version of that platform when it was first introduced.
Example
For an example platform of foo, this is how it should now render:
text
foo (instead of foo 2.0+)
title (hover text)
Available on foo (instead of Available on foo 2.0 and later)
aria-label
foo, Available on foo (same pattern of combining text/title)
Testing
Steps:
introducedAt
value from existing availability itemsChecklist
Make sure you check off the following items. If they cannot be completed, provide a reason.
npm test
, and it succeeded