-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version Packages #2220
Version Packages #2220
Conversation
GeraldRequired Reviewers
Don't want to be involved in this pull request? Comment |
Size Change: 0 B Total Size: 96.1 kB ℹ️ View Unchanged
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2220 +/- ##
==========================================
+ Coverage 94.47% 95.66% +1.18%
==========================================
Files 248 248
Lines 29229 29229
Branches 1638 2447 +809
==========================================
+ Hits 27614 27961 +347
+ Misses 1611 1252 -359
- Partials 4 16 +12 see 43 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
0fdba99
to
d08485d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@khanacademy/[email protected]
Major Changes
useScheduledTimeout
has been renamed touseTimeout
and the originaluseTimeout
has been removed. To update existing uses ofuseTimeout
to the new API: ifactive
wastrue
just delete that argument or replace it with{schedulingPolicy: SchedulingPolicy.Immediately}
; ifactive
wasfalse
replace it with{schedulingPolicy: SchedulingPolicy.OnDemand}
.useScheduledInterval
has been renamed touseInterval
and the originaluseInterval
has been removed. To update existing uses ofuseInterval
to the new API: ifactive
wastrue
just delete that argument or replace it with{schedulingPolicy: SchedulingPolicy.Immediately}
; ifactive
wasfalse
replace it with{schedulingPolicy: SchedulingPolicy.OnDemand}
.useTimeout
now supports an optionalActionPolicy
in the options. The default is to not reset the timeout when theaction
callback changes. This can be changed toActionPolicy.Reset
to reset the timeout when theaction
callback changes (it is recommended that you useuseCallback
on youraction
callback to avoid resetting the timeout everytime a component renders when using theReset
policy).useInterval
now supports an optionalActionPolicy
in the options. The default is to not reset the interval when theaction
callback changes. This can be changed toActionPolicy.Reset
to reset the interval when theaction
callback changes (it is recommended that you useuseCallback
on youraction
callback to avoid resetting the interval everytime a component renders when using theReset
policy).useTimeout
will now correctly reset the timeout when theset
method is called, as intended.useInterval
will now correctly reset the interval when theset
method is called, as intended.@khanacademy/[email protected]
Minor Changes
Listbox
component with Single and Multiple selection supportPatch Changes
@khanacademy/[email protected]
Patch Changes
@khanacademy/[email protected]
Patch Changes
@khanacademy/[email protected]
Patch Changes
@khanacademy/[email protected]
Patch Changes