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(#19): Manage exceptions by default and allow the gem's consumer to manage them by itself #20

Merged
merged 3 commits into from
Dec 12, 2023

Conversation

jcagarcia
Copy link
Owner

@jcagarcia jcagarcia commented Dec 9, 2023

With this PR, the gem will be configurable for handling potential Redis exceptions. Consequently, if a Redis exception occurs, the idempotent behavior will be compromised, yet the application will remain stable without crashing.

Also, if some exception appears after the code is executed, instead of raising the idempotent behavior will be compromised and we will return 409 Conflict in the next call with the same idempotency key.

README.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
@jcagarcia jcagarcia merged commit fe1cd22 into main Dec 12, 2023
3 checks passed
@jcagarcia jcagarcia deleted the issue-19 branch December 12, 2023 09:49
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.

Allow to decide if redis exceptions should be treated as no idempotent operation
2 participants