feat: contract composer apis #2
Conversation
model/equaliq.smithy
Outdated
| @@ -27,6 +27,12 @@ service EqualIQ { | |||
| GetContractSignatures | |||
| UpdateSignatureStatus | |||
| DeleteContractSignature | |||
| CreateComposerContract | |||
| UpdateComposerContract | |||
There was a problem hiding this comment.
Should we split out different kinds of updates?
model/equaliq.smithy
Outdated
| CreateComposerContract | ||
| UpdateComposerContract | ||
| ListComposerContracts | ||
| GetComposerContract |
There was a problem hiding this comment.
Should we split different kinds of Gets? Maybe we should use Meta vs Content?
| @@ -27,6 +27,12 @@ service EqualIQ { | |||
| GetContractSignatures | |||
| UpdateSignatureStatus | |||
| DeleteContractSignature | |||
| CreateComposerContract | |||
There was a problem hiding this comment.
Should we use smithy Resources?
model/equaliq.smithy
Outdated
| @@ -98,6 +104,18 @@ enum SignContractResult { | |||
| FAILURE | |||
| } | |||
|
|
|||
| enum ComposerContractStatus { | |||
| DRAFT | |||
| FINALIZED | |||
There was a problem hiding this comment.
I think we should treat this more like a cache structure for now:
NEW
CLEAN_IN_VAULT
DIRTY
ARCHIVED
model/equaliq.smithy
Outdated
| sectionId: String | ||
| name: String | ||
| content: String | ||
| plainTextSummary: String |
There was a problem hiding this comment.
Let's leave this in the frontend for now
model/equaliq.smithy
Outdated
| @@ -698,3 +716,130 @@ structure DeleteContractSignatureOutput { | |||
| message: String | |||
| } | |||
|
|
|||
|
|
|||
| structure ComposerContractSection { | |||
| sectionId: String | |||
model/equaliq.smithy
Outdated
| structure ComposerContractSection { | ||
| sectionId: String | ||
| name: String | ||
| content: String |
There was a problem hiding this comment.
Instead of 'name'/'content' let's add specific structured type for each section with the required fields.
model/equaliq.smithy
Outdated
| } | ||
|
|
||
| list ComposerContractList { | ||
| member: ComposerContract |
There was a problem hiding this comment.
Let's split out a Metadata type so that we don't need the full composer data for every item in the list
model/equaliq.smithy
Outdated
| @required | ||
| title: String | ||
| @required | ||
| type: ContractType |
There was a problem hiding this comment.
We should take the input form details as well
…k as they were not exporting properly but built fine
No description provided.