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: return an result error during serialization and deserialization #141

Conversation

vincent-herlemont
Copy link
Owner

@vincent-herlemont vincent-herlemont self-assigned this May 4, 2024
@vincent-herlemont vincent-herlemont force-pushed the return-an-result-error-during-serialization-and-deserialization branch 2 times, most recently from 4db2027 to 4ffb739 Compare May 15, 2024 15:35
@vincent-herlemont vincent-herlemont force-pushed the return-an-result-error-during-serialization-and-deserialization branch 2 times, most recently from 39d4654 to 616f0d3 Compare May 20, 2024 14:41
Now all queries are returning a `Result` error during serialization and deserialization.

Note: better to use `try_collect` instead of `collect` provided by the `itertools` crate
      queries are returning a iterator of `Result`.
@vincent-herlemont vincent-herlemont force-pushed the return-an-result-error-during-serialization-and-deserialization branch from 616f0d3 to ca42c1d Compare May 20, 2024 15:30
@vincent-herlemont vincent-herlemont changed the title fix: return an result error during serialization and deserialization feat: return an result error during serialization and deserialization May 20, 2024
@vincent-herlemont vincent-herlemont merged commit 9fae603 into main May 20, 2024
9 checks passed
@vincent-herlemont vincent-herlemont deleted the return-an-result-error-during-serialization-and-deserialization branch May 20, 2024 15:43
@vincent-herlemont
Copy link
Owner Author

🎉 This PR is included in version 0.7.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant