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

make NoopClient feature dependant #1380

Merged

Conversation

demoray
Copy link
Contributor

@demoray demoray commented Sep 14, 2023

Instead of always compiling in NoopClient, make it something that's only available if the reqwest features were not enabled.

Instead of always compiling in NoopClient, make it something that's only
available if the reqwest clients were not enabled.
Copy link
Member

@heaths heaths left a comment

Choose a reason for hiding this comment

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

The code looks fine, but I don't understand what point is there in using the SDK if you have a client that does nothing? What's the intended use case? More of a meta question, though, and shouldn't block this PR. We can discuss on Teams, or here on this GitHub PR/issue.

@demoray
Copy link
Contributor Author

demoray commented Sep 15, 2023

The original intent was to enable working towards supporting wasm. For reference, this work was originally done in #939. With the changes in #1367, we likely can look to get rid of NoopClient soon.

@demoray demoray merged commit 1dca228 into Azure:main Sep 15, 2023
19 checks passed
@demoray demoray deleted the dont-compile-in-noop-client-unless-needed branch September 15, 2023 18:24
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