DateCalendar
, DateRangeCalendar
: move to private APIs
#70681
Merged
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?
Mark the
DateCalendar
andDateRangeCalendar
components recently added in #70578 as private APIs of the@wordpress/components
package, instead of being public.cc @chihsuan
Why?
The components are initially needed by the
@wordpress/dataviews
package, which will serve as a testing ground for the components before eventually marking them as public.How?
Tweaked how the components are exported — from the public
index.ts
file to theprivate-apis.ts
file (exported behinglock
call).I also tweaked the relevant README and JSDocs.
Testing Instructions
DateCalendar
,DateRangeCalendar
(and theTZDate
utility) can't be imported directly from@wordpress/components
unlock
function