-
Notifications
You must be signed in to change notification settings - Fork 493
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
I get feedback when source or target attribute of <camunda:in/> element has trailing whitespace #720
Labels
Milestone
Comments
Why not simply remove trailing or leading whitespace? Update: This is exactly what the customer suggests, too. |
nikku
added
ready
Ready to be worked on
Camunda 7
Flags an issue as related to Camunda Automation Platform 7
and removed
backlog
Queued in backlog
labels
Apr 5, 2018
philippfromme
added
in progress
Currently worked on
and removed
ready
Ready to be worked on
labels
Apr 10, 2018
philippfromme
added a commit
to bpmn-io/bpmn-js-properties-panel
that referenced
this issue
Apr 10, 2018
philippfromme
added
needs review
Review pending
and removed
in progress
Currently worked on
labels
Apr 10, 2018
philippfromme
added a commit
to bpmn-io/bpmn-js-properties-panel
that referenced
this issue
Apr 11, 2018
philippfromme
added a commit
to bpmn-io/bpmn-js-properties-panel
that referenced
this issue
Apr 11, 2018
We've decided to validate instead of automatically trimming whitespace, as the later was too much magic. |
Fails locally and on CI. |
nikku
pushed a commit
to bpmn-io/bpmn-js-properties-panel
that referenced
this issue
Apr 11, 2018
I've fixed the minor issue that made the stuff fail on CI. Further change is needed though:
I've updated the issue description accordingly. |
philippfromme
added a commit
to bpmn-io/bpmn-js-properties-panel
that referenced
this issue
Apr 11, 2018
philippfromme
added
needs review
Review pending
and removed
ready
Ready to be worked on
labels
Apr 11, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Context:
Expected behavior:
source
ortarget
source expression
Cf. SUPPORT-3961
The text was updated successfully, but these errors were encountered: