-
Notifications
You must be signed in to change notification settings - Fork 205
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
Make Template ID optional in exercise; exercise by key #2695
Conversation
I'm not convinced that is a good idea. What's the rationale for doing it? |
@hurryabit This refers only to the HTTP JSON API; contract ID is sufficient to disambiguate. As a rule we don't require anything we can derive in the HTTP JSON API. |
Can we close this? |
@hurryabit we want to finish it, but it is not our top priority. Current priorities (sorted): |
* Lookup by Contract ID and Contract Key is WIP * factor out "contract ID or key" JSON decoding - adapted from fc13225 (#2695) * Resolving conflicts * Resolving conflicts * Lookup by contract ID works * Testing new contract created by IOU_Transfer can be looked up * error if key and contractId specified for lookup at the same time * Lookup by contract key test * Lookup docs * re-format with `./fmt.sh` * minor cleanup CHANGELOG_BEGIN - [JSON API - Experimental] Fix and document ``/contracts/lookup`` endpoint. See #3755. CHANGELOG_END
Obsoleted by #4049. |
The exercise endpoint in HTTP JSON API currently requires a template ID, even when a contract ID is provided. In general for contract reference we want to support two forms:
We should support this for exercise as well as lookup (which already supports it).
Structurally dependent on #3755.
Pull Request Checklist
NOTE: CI is not automatically run on non-members pull-requests for security
reasons. The reviewer will have to comment with
/AzurePipelines run
totrigger the build.