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

feat: add a top-level method for accessing providers #1152

Merged
merged 2 commits into from
Mar 6, 2025
Merged

Conversation

beeme1mr
Copy link
Member

This PR

  • add a top-level method for accessing providers

Notes

While working on some improvements to the way Suspense works in the React SDK, I ran into a few scenarios were having access to the provider itself was important. I needed a way to confidently tell that a provider was the noop provider since it has special properties like never being in a ready state. There are a few ways could could achieve this but I noticed that the Java SDK already has methods that expose the provider. It also allowed me to improve some of our existing tests.

How to test

Unit tests have been updated accordingly.

@beeme1mr beeme1mr requested a review from a team as a code owner February 26, 2025 17:47
Copy link
Member

@toddbaert toddbaert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have this in Java and other SDKs, and since it's not on the client I think the chances of average application authors using it inappropriately is relatively low.

There's utility here enough to do it IMO.

Copy link
Member

@lukas-reining lukas-reining left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

@beeme1mr beeme1mr enabled auto-merge March 6, 2025 20:49
@beeme1mr beeme1mr added this pull request to the merge queue Mar 6, 2025
Merged via the queue into main with commit ae8fce8 Mar 6, 2025
9 checks passed
@beeme1mr beeme1mr deleted the expose-provider branch March 6, 2025 20:51
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.

3 participants