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

api: move WebPkiSupportedAlgorithms to crypto #1644

Merged
merged 1 commit into from
Nov 30, 2023

Conversation

jsha
Copy link
Contributor

@jsha jsha commented Nov 30, 2023

The top level of the crate is meant for "paved path" exports.

This newly exported type is used for cryptographic provider customization, so it properly belongs in the crypto module.

Related: #1435

Copy link

codecov bot commented Nov 30, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (3e74257) 95.71% compared to head (03ba0d9) 95.71%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1644   +/-   ##
=======================================
  Coverage   95.71%   95.71%           
=======================================
  Files          78       78           
  Lines       16094    16094           
=======================================
  Hits        15405    15405           
  Misses        689      689           

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

The top level of the crate is meant for "paved path" exports.

This newly exported type is used for cryptographic provider
customization, so it properly belongs in the `crypto` module.
@jsha jsha force-pushed the webpkisupportedalgorithms-not-top-level branch from ea9dddd to 03ba0d9 Compare November 30, 2023 00:27
@cpu cpu added this pull request to the merge queue Nov 30, 2023
Merged via the queue into rustls:main with commit d931562 Nov 30, 2023
22 of 23 checks passed
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.

4 participants