You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore: Remove CollectionNode default filter behavior and other release API updates (adobe#8761)
* chore: updating CollectionNode filter logic so it doesnt filter by default
* rename triggerOrigin to triggerAnchorPoint
* add docs for reset/setLocalTimeZone
* bold stuff
Copy file name to clipboardExpand all lines: packages/@internationalized/date/docs/CalendarDate.mdx
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,6 +50,8 @@ let date = parseDate('2022-02-03');
50
50
51
51
Today's date can be retrieved using the <TypeLinklinks={docs.links}type={docs.exports.today} /> function. This requires a time zone identifier to be provided, which is used to determine the local date. The <TypeLinklinks={docs.links}type={docs.exports.getLocalTimeZone} /> function can be used to retrieve the user's current time zone.
52
52
53
+
**Note:** the local time zone is cached after the first call. You can reset it by calling <TypeLinklinks={docs.links}type={docs.exports.resetLocalTimeZone} />, or mock it in unit tests by calling <TypeLinklinks={docs.links}type={docs.exports.setLocalTimeZone} />.
@@ -206,6 +208,8 @@ A `CalendarDate` can be converted to a native JavaScript `Date` object using the
206
208
207
209
Because a `Date` represents an exact time, a time zone identifier is required to be passed to the `toDate` method. The time of the returned date will be set to midnight in that time zone. The <TypeLinklinks={docs.links}type={docs.exports.getLocalTimeZone} /> function can be used to retrieve the user's current time zone.
208
210
211
+
**Note:** the local time zone is cached after the first call. You can reset it by calling <TypeLinklinks={docs.links}type={docs.exports.resetLocalTimeZone} />, or mock it in unit tests by calling <TypeLinklinks={docs.links}type={docs.exports.setLocalTimeZone} />.
Copy file name to clipboardExpand all lines: packages/@internationalized/date/docs/CalendarDateTime.mdx
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -280,6 +280,8 @@ A `CalendarDateTime` can be converted to a native JavaScript `Date` object using
280
280
281
281
Because a `Date` represents an exact time, a time zone identifier is required to be passed to the `toDate` method. The <TypeLinklinks={docs.links}type={docs.exports.getLocalTimeZone} /> function can be used to retrieve the user's current time zone.
282
282
283
+
**Note:** the local time zone is cached after the first call. You can reset it by calling <TypeLinklinks={docs.links}type={docs.exports.resetLocalTimeZone} />, or mock it in unit tests by calling <TypeLinklinks={docs.links}type={docs.exports.setLocalTimeZone} />.
Copy file name to clipboardExpand all lines: packages/@internationalized/date/docs/ZonedDateTime.mdx
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,6 +76,8 @@ let date = fromAbsolute(1688023843144, 'America/Los_Angeles');
76
76
77
77
The current time can be retrieved using the <TypeLinklinks={docs.links}type={docs.exports.now} /> function. This requires a time zone identifier to be provided, which is used to determine the local time. The <TypeLinklinks={docs.links}type={docs.exports.getLocalTimeZone} /> function can be used to retrieve the user's current time zone.
78
78
79
+
**Note:** the local time zone is cached after the first call. You can reset it by calling <TypeLinklinks={docs.links}type={docs.exports.resetLocalTimeZone} />, or mock it in unit tests by calling <TypeLinklinks={docs.links}type={docs.exports.setLocalTimeZone} />.
0 commit comments