-
Notifications
You must be signed in to change notification settings - Fork 6
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
fix(operate): use post request for decision definitions and decision instances endpoints #263
Conversation
Thanks for this. Can you open this against the |
…instances endpoints
5a22ecb
to
419ae56
Compare
@jwulf done 👍 |
src/operate/lib/OperateDto.ts
Outdated
@@ -40,6 +40,7 @@ export class DecisionInstance extends LosslessDto { | |||
evaluationFailure!: string | |||
@Int64String | |||
processDefinitionKey!: string | |||
processInstanceKey!: number |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be a string
, decorated with @Int64String
.
Camunda 8 entity keys (such as processInstanceKey
) are int64
in JSON and could be a value that cannot be accurately represented by the JS number type, so the Dtos enable lossless parsing with annotations - with the characteristic that C8 entity keys are strings in JS, rather than numbers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good to know. I was wondering why the keys were all strings when Operate API specified them as numbers
closes #262
DecisionInstance type should also include processInstanceKey, which is also addressed in this PR
Description of the change
[Describe your changes here]
Type of change
Checklist
alpha
branchFurther comments
[If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...]