-
Notifications
You must be signed in to change notification settings - Fork 3
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
Lexical dependency considered “unsound” #3
Comments
@backspace Not sure how I missed this issue, thanks for bringing it into my attention. |
@backspace I took a look into it today, and it looks like we might not be affected by the bug. But I think it would still make sense to dump lexical, since it looks unmaintained. |
I’m sorry, I don’t! I’m too new to Rust to be of help 😞 |
@backspace Thanks a lot for the report, that was more than enough buddy, no worries. I pushed a commit today and will hopefully release it soon. |
Hey, thanks for your work on this, I used it in an Axum application where I was receiving duplicate query parameters and your library could handle it, unlike the built-in extractor.
I’ve been getting security audit errors about the dependency on
lexical
:I’m pretty new to Rust and not that confident about attempting the suggested alternatives, but I could give it a try if you don’t have capacity. I assume this would be a breaking change 🤔
The text was updated successfully, but these errors were encountered: