-
Notifications
You must be signed in to change notification settings - Fork 17
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
Not find camunda:decisionRef change #2
Comments
May be fixed with latest version of this library. If that is not the case, add a pull request with a failing test case and we can fix this. |
This may happen when importing unknown extension namespaces, i.e. <camunda> without the moddle definition (camunda-bpmn-moddle). Related to #2
Hi! I upgraded to 0.3.0 version, but unfortunately it is still not tracing camunda:decisionRef changes nor input/output parameters. |
You'd need to add the camunda-bpmn-moddle extension in order to recognize camunda attributes. See this failing test case I've created. |
Thank you nikku! Now it trace camunda:decisionRef change indeed. I Used as following:
However it is still not tracing input/output parameter changes. |
Make sure you use the latest version of bpmn-moddle, too. We're at |
Ok, when I call |
Please provide a reproducible test case, including
Cf. this example |
test/fixtures/extension-attributes/before.bpmn
test/fixtures/extension-attributes/after.bpmn
test/spec/differ.js
I modified also BpmnModdle creation in the top of test/deffer.js to diff camunda specific namespace.
When I execute npm run test it prints all changed properties, but no information about input/output parameter changes. However if you look at before/after BPMN files, I also changed input/output parameters but in the "attrs array" they are not found. |
Hi, |
Hi!
The differ cannot find camunda:decisionRef changes.
Can it be that differ not works in case of camunda namespace?
The text was updated successfully, but these errors were encountered: