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

fix(deps): update dependency com.graphql-java:java-dataloader to v3.3.0 #25

Merged
merged 1 commit into from
Jul 12, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 10, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
com.graphql-java:java-dataloader 3.1.0 -> 3.3.0 age adoption passing confidence

Release Notes

graphql-java/java-dataloader (com.graphql-java:java-dataloader)

v3.3.0: 3.3.0

Compare Source

What's Changed

Full Changelog: graphql-java/java-dataloader@v3.2.2...v3.3.0

v3.2.2: 3.2.2

Compare Source

What's Changed

A series of small fixes to make the code more efficient

New Contributors

Full Changelog: graphql-java/java-dataloader@v3.2.1...v3.2.2

v3.2.1: 3.2.1

Compare Source

New ticker mode

There is a new mode in ScheduledDataLoaderRegistry called ticker mode that will continue to tick away and allow for chained data loader calls. See the readme for more details.

  ScheduledDataLoaderRegistry registry = ScheduledDataLoaderRegistry.newScheduledRegistry()
        .register("a", dataLoaderA)
        .register("b", dataLoaderB)
        .scheduledExecutorService(executorService)
        .schedule(Duration.ofMillis(10))
        .tickerMode(true) // ticker mode is on
        .build();

  CompletableFuture<Object> chainedCalls = dataLoaderA.load("user1")
        .thenCompose(userAsKey -> dataLoaderB.load(userAsKey));

Predicates per dataloader in ScheduledDataLoaderRegistry

ScheduledDataLoaderRegistry now has the capability to have a predicate per data loader specified as well as an overall one. This allows you to have fine control on when dataloaders get dispatched.

What's Changed

New Contributors

Full Changelog: graphql-java/java-dataloader@v3.2.0...v3.2.1

v3.2.0: 3.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: graphql-java/java-dataloader@v3.1.4...v3.2.0

v3.1.4: 3.1.4

Compare Source

What's Changed

New Contributors

Full Changelog: graphql-java/java-dataloader@v3.1.3...v3.1.4

v3.1.3: 3.1.3

Compare Source

What's Changed

New Contributors

Full Changelog: graphql-java/java-dataloader@v3.1.2...vv3.1.3

v3.1.2: 3.1.2

Compare Source

This fix release prevents excessive object allocation in the no-op ValueCache

v3.1.1: 3.1.1

Compare Source

Small bugs fixes and the ability to prime the cache


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/com.graphql-java-java-dataloader-3.x branch 18 times, most recently from b674589 to a87c1ae Compare July 12, 2024 07:27
@renovate renovate bot force-pushed the renovate/com.graphql-java-java-dataloader-3.x branch from a87c1ae to 984da57 Compare July 12, 2024 10:10
@renovate renovate bot merged commit 9a3d39b into main Jul 12, 2024
1 check passed
@renovate renovate bot deleted the renovate/com.graphql-java-java-dataloader-3.x branch July 12, 2024 13:15
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.

0 participants