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

Use crypto api import for CryptoCallbacks instead of legacy crypto #4526

Conversation

florianduros
Copy link
Contributor

@florianduros florianduros commented Nov 13, 2024

Checklist

  • Tests written for new code (and old code if feasible).
  • New or updated public/exported symbols have accurate TSDoc documentation.
  • Linter and other CI checks pass.
  • Sign-off given on the changes (see CONTRIBUTING.md).

The legacy crypto ICryptoCallback are already an reexport of the crypto api CryptoCallback.

@florianduros florianduros added this pull request to the merge queue Nov 13, 2024
Merged via the queue into develop with commit 52bdb57 Nov 13, 2024
35 checks passed
@florianduros florianduros deleted the florianduros/rip-out-legacy-crypto/use-crypto-api-cryptocallback branch November 13, 2024 11:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Task Tasks for the team like planning
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants