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

Uses CtapResult instead of explicit Result #696

Merged
merged 1 commit into from
Jul 25, 2024

Conversation

kaczmarczyck
Copy link
Collaborator

Generated with

find . -type f -name "*.rs" -exec sed -i 's/Result<\([^,]*\), Ctap2StatusCode>/CtapResult<\1>/g' {} \;
cd libraries/opensk
find . -type f -name "*.rs" -exec grep -q 'CtapResult' {} \; -exec sed -i '15 i\
use crate::ctap::status_code::CtapResult;
' {} +

Then we fix the last few compiler errors and run cargo fmt.

Next step is to move away from custom error types in the API to only use CtapResult everywhere.

@kaczmarczyck kaczmarczyck requested a review from ia0 July 25, 2024 12:04
Generated with

```
find . -type f -name "*.rs" -exec sed -i 's/Result<\([^,]*\), Ctap2StatusCode>/CtapResult<\1>/g' {} \;
cd libraries/opensk
find . -type f -name "*.rs" -exec grep -q 'CtapResult' {} \; -exec sed -i '15 i\
use crate::ctap::status_code::CtapResult;
' {} +
```

Then we fix the last few compiler errors and run `cargo fmt`.

Next step is to move away from custom error types in the API to only use
CtapResult everywhere.
@kaczmarczyck kaczmarczyck merged commit 4c23e61 into google:develop Jul 25, 2024
9 checks passed
@kaczmarczyck kaczmarczyck deleted the ctap-result-refactoring branch July 25, 2024 12:27
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