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

Map the intended delays to the nearest supported delay #158

Merged
merged 2 commits into from
Aug 15, 2024

Conversation

Le-Merle
Copy link
Contributor

Description of changes

When releasing an event lock in the Pull Delivery mode, it is possible to specify a release delay.

It turns out that the API allows an int, but will only support specific values for that parameter. This PR maps the intended delays to the nearest supported delay by the API, in order to prevent errors.

Breaking changes

None

Additional checks

  • Updated the documentation of the project to reflect the changes
  • Added new tests that cover the code changes

@Le-Merle Le-Merle requested a review from a team as a code owner August 14, 2024 18:26
@Le-Merle Le-Merle merged commit 163c3bd into main Aug 15, 2024
4 checks passed
@Le-Merle Le-Merle deleted the feature/SGCORE-863_Use-Valid-Release-Retry-Delays branch August 15, 2024 13:13
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.

3 participants