Skip to content
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

Various fixes as I attempted to get our CR-Connect application working against the lastest SpiffWorkflow build #247

Merged
merged 4 commits into from
Oct 10, 2022

Conversation

danfunk
Copy link
Collaborator

@danfunk danfunk commented Oct 7, 2022

  1. spec_type should be the type only, and should not reflect event defitions ('End Event' not 'Default End Event')
  2. MultInstance functions as a mixin, and should not overwrite the spec_type, a repeating User Task is still a User Task
  3. We implemented "Did you mean ..." twice - and with the latest changes to the PythonScriptEngine.py and DMNEngine.py, we can do it once. - Removed the check in the DMNEngine, and improved in exceptions.py
  4. The Python Script engines "evaluate" method should accept external methods as an optional argument.
  5. The Levenshtein function should return a list, not a list coverted to a string.
  6. For the base excetion handler, don't stuff the name of the task infront of the error, it's passed along as the sender - no need to alter the message.

…fitions ('End Event' not 'Default End Event')

2) MultInstance functions as a mixin, and should not overwrite the spec_type, a releating User Task is stil a User Task
3) We implemented "Did you mean ..." twice - and with the latest changes to the PythonScriptEngine.py and DMNEngine.py, we can do it once.  - Removed the check in the DMNEngine, and improved in exceptions.py
4) The Python Script engines "evaluate" method should accept external methods.
5) The Levenshtein function should return a list, not a list coverted to a string.
6) For the base excetion handler, don't stuff the name of the task infront of the error, it's passed along as the sender - no need to alter the message.
1. white space formatting
2. empty except statements
3. camel casing variables (when it doesn't impact serialization)
4. create constants when a string is used multiple times.
5. add comments when methods are completely empty
6. and other minor business
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 9 Code Smells

84.0% 84.0% Coverage
0.0% 0.0% Duplication

@danfunk danfunk merged commit f30221d into main Oct 10, 2022
@danfunk danfunk deleted the bug/release_fixes branch October 10, 2022 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants