Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / jcagarcia/grape-idempotency issues and pull requests

#19 - Allow to decide if redis exceptions should be treated as no idempotent operation

Issue - State: closed - Opened by jcagarcia about 1 year ago
Labels: improvement

#19 - Allow to decide if redis exceptions should be treated as no idempotent operation

Issue - State: closed - Opened by jcagarcia about 1 year ago
Labels: improvement

#18 - Release 1.0.0 version

Pull Request - State: closed - Opened by jcagarcia about 1 year ago

#18 - Release 1.0.0 version

Pull Request - State: closed - Opened by jcagarcia about 1 year ago

#16 - Return Unprocessable Entity error for conflict

Pull Request - State: closed - Opened by Flip120 over 1 year ago - 1 comment

#16 - Return Unprocessable Entity error for conflict

Pull Request - State: closed - Opened by Flip120 over 1 year ago - 1 comment

#15 - feature(#14): Allow to make idempotency key header mandatory

Pull Request - State: closed - Opened by jcagarcia over 1 year ago

#15 - feature(#14): Allow to make idempotency key header mandatory

Pull Request - State: closed - Opened by jcagarcia over 1 year ago

#14 - Make Idempotency-Key header mandatory

Issue - State: closed - Opened by jcagarcia over 1 year ago
Labels: enhancement, help wanted, good first issue

#14 - Make Idempotency-Key header mandatory

Issue - State: closed - Opened by jcagarcia over 1 year ago
Labels: enhancement, help wanted, good first issue

#13 - Return 422 Unprocessable Entity if there is an attempt to reuse an idempotency key with a different request payload

Issue - State: closed - Opened by jcagarcia over 1 year ago - 1 comment
Labels: help wanted, improvement

#12 - Allow to configure logger

Issue - State: closed - Opened by jcagarcia over 1 year ago
Labels: enhancement, help wanted, good first issue

#12 - Allow to configure logger

Issue - State: closed - Opened by jcagarcia over 1 year ago
Labels: enhancement, help wanted, good first issue

#11 - Add processing response

Pull Request - State: closed - Opened by Flip120 over 1 year ago

#11 - Add processing response

Pull Request - State: closed - Opened by Flip120 over 1 year ago

#10 - Two requests with idempotency key are performing the code when one of the requests didn't finish yet

Issue - State: closed - Opened by jcagarcia over 1 year ago - 2 comments
Labels: enhancement, help wanted, good first issue

#10 - Two requests with idempotency key are performing the code when one of the requests didn't finish yet

Issue - State: closed - Opened by jcagarcia over 1 year ago - 2 comments
Labels: enhancement, help wanted, good first issue

#9 - Store valid response when error is raised and managed in rescue_from handler

Pull Request - State: closed - Opened by jcagarcia over 1 year ago
Labels: fix

#9 - Store valid response when error is raised and managed in rescue_from handler

Pull Request - State: closed - Opened by jcagarcia over 1 year ago
Labels: fix

#8 - bug: When conflict appears, the response is returned as a String

Issue - State: closed - Opened by jcagarcia over 1 year ago - 1 comment
Labels: bug

#7 - bug: Second call returns `null` when the first response was generated inside a `rescue_from`

Issue - State: closed - Opened by jcagarcia over 1 year ago - 1 comment
Labels: bug, help wanted

#6 - fix(#5): Prevent to change the response if the endpoint returns a hash

Pull Request - State: closed - Opened by jcagarcia over 1 year ago

#5 - bug: When the endpoint is returning a hash, the second request returns null

Issue - State: closed - Opened by jcagarcia over 1 year ago
Labels: bug

#2 - Configuring workflows

Pull Request - State: closed - Opened by jcagarcia over 1 year ago

#1 - Initial commit

Pull Request - State: closed - Opened by jcagarcia over 1 year ago