Skip to content
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

ci(changesets): refine registry version packages #6638

Merged
merged 1 commit into from
Jan 9, 2025

Conversation

refine-bot
Copy link
Contributor

@refine-bot refine-bot commented Jan 7, 2025

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 next, this PR will be updated.

Releases

@refinedev/[email protected]

Patch Changes

Refine Enterprise Release

  • #6626 087039f0ccd13e9fe5bf4ef904e4f1c2df129d69 Thanks @aliemir! - feat(core): add enabled prop to useLoadingOvertime and overtimeOptions

    Added missing enabled prop to useLoadingOvertime and added ability to globally configure through options.overtime.enabled.

    Due to the nature of calculating elapsed time, an interval is set by the interval prop. This was causing unwanted updates in the return value and there was no way to disable it properly.

Refine Enterprise Release

  • #6626 087039f0ccd13e9fe5bf4ef904e4f1c2df129d69 Thanks @aliemir! - refactor(core): remove duplicated overtime intervals caused by internally used hooks

    Updated Refine's data hooks and extensions to prevent duplicated overtime intervals from being created. This uses the enabled prop to prevent internal hooks from registering the intervals.

    Prior to this change, useTable was initializing its own useLoadingOvertime hook but also propagated the elapsedTime from useList hook which is used internally by useTable. This caused duplicated intervals and unwanted updates.

    This now ensures a single interval is created and used for the extension hooks.

@refinedev/[email protected]

Patch Changes

Refine Enterprise Release

@refinedev/[email protected]

Patch Changes

Refine Enterprise Release

@refine-bot refine-bot requested a review from a team as a code owner January 7, 2025 08:05
@refine-bot refine-bot force-pushed the changeset-release/next branch from aac2e5a to d711a3d Compare January 7, 2025 08:19
Copy link
Contributor

github-actions bot commented Jan 7, 2025

Copy link

cypress bot commented Jan 7, 2025

refine    Run #11824

Run Properties:  status check passed Passed #11824  •  git commit 4de5f10198 ℹ️: Merge d711a3dcf2475ff5564b8389fdd53d198ffc9272 into 2f5ad1e7d0faaa543fe1a003c7ec...
Project refine
Branch Review changeset-release/next
Run status status check passed Passed #11824
Run duration 18m 36s
Commit git commit 4de5f10198 ℹ️: Merge d711a3dcf2475ff5564b8389fdd53d198ffc9272 into 2f5ad1e7d0faaa543fe1a003c7ec...
Committer Refine Community Bot
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 22
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 378
View all changes introduced in this branch ↗︎

@BatuhanW BatuhanW merged commit 98b9892 into next Jan 9, 2025
97 checks passed
@BatuhanW BatuhanW deleted the changeset-release/next branch January 9, 2025 07:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants