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: implement optional reqwest depdendency for smaller deps #21

Closed
wants to merge 2 commits into from

Conversation

latonis
Copy link
Contributor

@latonis latonis commented Feb 26, 2024

As discussed in #9, I've gone ahead and declared reqwest an optional dependency using features. By default, I've kept it as a dependency and users can opt out of using it and installing the dependencies by declaring default-features false.

cryptographic-message-syntax = { version = "0.26.0", default-features = false }

@latonis
Copy link
Contributor Author

latonis commented Mar 19, 2024

@indygreg, I believe this accomplishes what #9 is looking for whenever you have time to review 😸 crate stays the same, only the dependencies change based on features

Copy link
Owner

@indygreg indygreg left a comment

Choose a reason for hiding this comment

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

Thank you!

I'm rebasing this locally since it now has merge conflicts. Should push + release in the next few hours.

@indygreg indygreg closed this in f16f50e Nov 2, 2024
indygreg pushed a commit that referenced this pull request Nov 2, 2024
This slims down the dependency tree significantly if the feature
is disabled.

Closes #21.
@latonis latonis deleted the cms-features branch November 2, 2024 23:53
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