Skip to content

Version Packages#3337

Merged
ntucker merged 1 commit intomasterfrom
changeset-release/master
Feb 24, 2025
Merged

Version Packages#3337
ntucker merged 1 commit intomasterfrom
changeset-release/master

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions bot commented Dec 29, 2024

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

Releases

@data-client/core@0.14.19

Patch Changes

  • #3343 1df829e Thanks @ntucker! - Add initManager()

  • #3373 f796b6c Thanks @ntucker! - Add Controller.getQueryMeta and Controller.getResponseMeta

  • #3373 f796b6c Thanks @ntucker! - Controller.snapshot() methods have stronger argument typing

  • #3365 66e7336 Thanks @ntucker! - internal: Controller.bindMiddleware() to be used in applyMiddleware.

    This API is not intended to be used elsewhere, but will become the standard interface between
    Controller's and applyMiddleware.

  • #3343 1df829e Thanks @ntucker! - Add GCPolicy to control Garbage Collection of data in the store.

    This can be configured with constructor options, or custom GCPolicies implemented by extending
    or simply building your own. Use ImmortalGCPolicy to never GC (to maintain existing behavior).

    constructor

    intervalMS = 60 * 1000 * 5

    How long between low priority GC sweeps.

    Longer values may result in more memory usage, but less performance impact.

    expiryMultiplier = 2

    Used in the default hasExpired policy.

    Represents how many 'stale' lifetimes data should persist before being
    garbage collected.

    expiresAt

    expiresAt({
        fetchedAt,
        expiresAt,
    }: {
      expiresAt: number;
      date: number;
      fetchedAt: number;
    }): number {
      return (
        Math.max(
          (expiresAt - fetchedAt) * this.options.expiryMultiplier,
          120000,
        ) + fetchedAt
      );
    }

    Indicates at what timestamp it is acceptable to remove unused data from the store.

    Data not currently rendered in any components is considered unused. However, unused
    data may be used again in the future (as a cache).

    This results in a tradeoff between memory usage and cache hit rate (and thus performance).

  • #3371 679d76a Thanks @ntucker! - Add react-native entry to package.json exports

  • #3353 165afed Thanks @renovate! - Polyfills no longer pollute global scope

  • Updated dependencies [679d76a, 165afed]:

    • @data-client/normalizr@0.14.19

@data-client/endpoint@0.14.19

Patch Changes

@data-client/graphql@0.14.19

Patch Changes

@data-client/img@0.14.19

Patch Changes

@data-client/normalizr@0.14.19

Patch Changes

@data-client/react@0.14.19

Patch Changes

  • #3343 1df829e Thanks @ntucker! - Add gcPolicy option to DataProvider and prepareStore

    // run GC sweep every 10min
    <DataProvider gcPolicy={new GCPolicy({ intervalMS: 60 * 1000 * 10 })}>
      {children}
    </DataProvider>
    const { store, selector, controller } = prepareStore(
      initialState,
      managers,
      Controller,
      otherReducers,
      extraMiddlewares,
      gcPolicy: new GCPolicy({ intervalMS: 60 * 1000 * 10 }),
    );

    To maintain existing behavior, use ImmortalGCPolicy:

    import { ImmortalGCPolicy, DataProvider } from '@data-client/react';
    
    <DataProvider gcPolicy={new ImmortalGCPolicy()}>{children}</DataProvider>;
  • #3343 1df829e Thanks @ntucker! - Add GCPolicy to control Garbage Collection of data in the store.

    This can be configured with constructor options, or custom GCPolicies implemented by extending
    or simply building your own. Use ImmortalGCPolicy to never GC (to maintain existing behavior).

    constructor

    intervalMS = 60 * 1000 * 5

    How long between low priority GC sweeps.

    Longer values may result in more memory usage, but less performance impact.

    expiryMultiplier = 2

    Used in the default hasExpired policy.

    Represents how many 'stale' lifetimes data should persist before being
    garbage collected.

    expiresAt

    expiresAt({
        fetchedAt,
        expiresAt,
    }: {
      expiresAt: number;
      date: number;
      fetchedAt: number;
    }): number {
      return (
        Math.max(
          (expiresAt - fetchedAt) * this.options.expiryMultiplier,
          120000,
        ) + fetchedAt
      );
    }

    Indicates at what timestamp it is acceptable to remove unused data from the store.

    Data not currently rendered in any components is considered unused. However, unused
    data may be used again in the future (as a cache).

    This results in a tradeoff between memory usage and cache hit rate (and thus performance).

  • #3371 679d76a Thanks @ntucker! - Add react-native entry to package.json exports

  • 12bb010 Thanks @ntucker! - Update async boundary link in BackupLoading component

  • #3353 165afed Thanks @renovate! - Polyfills no longer pollute global scope

  • Updated dependencies [1df829e, f796b6c, f796b6c, 66e7336, 1df829e, 679d76a, 165afed]:

    • @data-client/core@0.14.19
    • @data-client/use-enhanced-reducer@0.1.12

@data-client/rest@0.14.19

Patch Changes

@data-client/test@0.14.19

Patch Changes

  • 060d8e1 Thanks @ntucker! - Update @testing-library/react-native to v13

  • #3365 66e7336 Thanks @ntucker! - fix: Interceptors work on manager-dispatched actions.

    For example, renderHook now can use resolverFixtures to resolve fetches for subscriptions.
    This was not possible before as SubscriptionManager's dispatches would not be intercepted with the
    previous implementation.

  • #3371 679d76a Thanks @ntucker! - Add react-native entry to package.json exports

  • #3353 165afed Thanks @renovate! - Polyfills no longer pollute global scope

@data-client/use-enhanced-reducer@0.1.12

Patch Changes

example-benchmark@0.4.68

Patch Changes

normalizr-github-example@0.1.46

Patch Changes

  • Updated dependencies [cb4fb92, 679d76a, 165afed]:
    • @data-client/endpoint@0.14.19
    • @data-client/normalizr@0.14.19

normalizr-redux-example@0.1.44

Patch Changes

  • Updated dependencies [cb4fb92, 679d76a, 165afed]:
    • @data-client/endpoint@0.14.19
    • @data-client/normalizr@0.14.19

normalizr-relationships@0.1.46

Patch Changes

  • Updated dependencies [cb4fb92, 679d76a, 165afed]:
    • @data-client/endpoint@0.14.19
    • @data-client/normalizr@0.14.19

@codecov
Copy link
Copy Markdown

codecov bot commented Dec 29, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.74%. Comparing base (08c1dd2) to head (04e81e8).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3337   +/-   ##
=======================================
  Coverage   98.74%   98.74%           
=======================================
  Files         136      136           
  Lines        2381     2381           
  Branches      488      488           
=======================================
  Hits         2351     2351           
  Misses         16       16           
  Partials       14       14           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@github-actions github-actions bot force-pushed the changeset-release/master branch 7 times, most recently from 68304ce to 39a6079 Compare January 3, 2025 20:06
@github-actions github-actions bot force-pushed the changeset-release/master branch 4 times, most recently from b319aad to a8ab71e Compare January 6, 2025 21:20
@github-actions github-actions bot force-pushed the changeset-release/master branch 3 times, most recently from d3d478c to 84f67a6 Compare January 8, 2025 20:16
@github-actions github-actions bot force-pushed the changeset-release/master branch 4 times, most recently from bb3e529 to 28eabaa Compare January 21, 2025 19:51
@github-actions github-actions bot force-pushed the changeset-release/master branch 2 times, most recently from df961a1 to 14f0897 Compare January 25, 2025 21:39
@github-actions github-actions bot force-pushed the changeset-release/master branch 8 times, most recently from fa0e574 to 93c8f9a Compare February 17, 2025 17:24
@github-actions github-actions bot force-pushed the changeset-release/master branch 2 times, most recently from a0d26ef to b76143d Compare February 17, 2025 17:29
@github-actions github-actions bot force-pushed the changeset-release/master branch 15 times, most recently from 93199f2 to 26590b1 Compare February 24, 2025 16:38
@github-actions github-actions bot force-pushed the changeset-release/master branch 2 times, most recently from 033558e to 6055272 Compare February 24, 2025 20:58
@github-actions github-actions bot force-pushed the changeset-release/master branch from 6055272 to 04e81e8 Compare February 24, 2025 21:00
@ntucker ntucker enabled auto-merge February 24, 2025 21:04
@ntucker ntucker added this pull request to the merge queue Feb 24, 2025
Merged via the queue into master with commit 9267432 Feb 24, 2025
18 checks passed
@ntucker ntucker deleted the changeset-release/master branch February 24, 2025 21:08
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.

1 participant