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

remove allowable close after order #192

Merged
merged 1 commit into from
Mar 6, 2024

Conversation

kirahsapong
Copy link
Contributor

brings to parity with tbdex-js

Copy link

codecov bot commented Mar 6, 2024

Codecov Report

Merging #192 (13c6de0) into main (fc4cd3d) will not change coverage.
The diff coverage is 100.00%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #192   +/-   ##
=======================================
  Coverage   77.60%   77.60%           
=======================================
  Files          33       33           
  Lines         817      817           
  Branches       79       79           
=======================================
  Hits          634      634           
  Misses        137      137           
  Partials       46       46           
Components Coverage Δ
protocol 82.93% <100.00%> (ø)
httpclient 80.46% <ø> (ø)

Copy link
Contributor

@KendallWeihe KendallWeihe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Edit: I misunderstood. Disregard below! Apologies! (we're stating that Close is not valid after Order but is valid after OrderStatus)


So the idea here being to bring to parity with tbdex-js, but to subsequently re-add support for a Close after an Order wherein the Close must have the success boolean property set, do I have that right?

(I added a summarization: TBD54566975/tbdex#242 (comment))

@kirahsapong kirahsapong merged commit 1cc37f4 into main Mar 6, 2024
5 of 6 checks passed
@kirahsapong kirahsapong deleted the feat/remove-close-after-order branch March 6, 2024 16:37
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.

5 participants