sartography / sartography/SpiffWorkflow
Default BoundaryEvent ValidationException
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 343
- Avg merge
- 2h 54m
- Merged PRs (30d)
- 1
Description
When a default Boundary Event is added to, say a Service Task, the validation exception is presented as a format string with xml inside a nested exception (i think) instead of a human readable message:
ValidationException: NotImplementedError('Unsupported Catch Event: %r', b'<bpmn:boundaryEvent xmlns:bpmn="http://www.omg.org/spec/BPMN/20100524/MODEL" xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" xmlns:dc="http://www.omg.org/spec/DD/20100524/DC" xmlns:di="http://www.omg.org/spec/DD/20100524/DI" xmlns:spiffworkflow="http://spiffworkflow.org/bpmn/schema/1.0/core" id="Event_1twii2v" attachedToRef="Task_1781606460703"/>\n ').
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the validation failure by adding a default Boundary Event to a Service Task, then trace the validation and nested exception handling that produces the displayed message. Done means the exception presents a human-readable message instead of an unformatted string containing the BPMN XML.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100