-
Notifications
You must be signed in to change notification settings - Fork 319
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
external dependencies #217
Conversation
…ading up files for parsing.
"""Locate all calls to external BPMN and DMN files, and store their | ||
ids in our list of dependencies""" | ||
for call_activity in xpath('.//bpmn:callActivity'): | ||
self.dependencies.append(call_activity.get('calledElement')) |
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.
Not sure if you can get into a situation where you have duplicate dependencies, like multiple callActivity nodes that have the same calledElement? If so, perhaps a set for the dependencies?
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.
excellent point, I'll assure it's a unique set.
Allow accessing process dependencies and dmn dependencies separately.
Because DMN references vary between Camunda and Spiff, need to test that | ||
both methods will work. | ||
""" | ||
|
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.
For the record, I don't like camunda and spiff appearing here, though given the way our test suite is set up, there probably isn't a better way.
Kudos, SonarCloud Quality Gate passed! |
Allows you to check which dependencies exist after adding one or more files to the BPMN parser.