Skip to content
This repository has been archived by the owner on Dec 2, 2021. It is now read-only.

Implement inputs & outputs group #54

Closed
Tracked by #2
barmac opened this issue Aug 3, 2021 · 2 comments · Fixed by #100
Closed
Tracked by #2

Implement inputs & outputs group #54

barmac opened this issue Aug 3, 2021 · 2 comments · Fixed by #100
Assignees

Comments

@barmac
Copy link
Member

barmac commented Aug 3, 2021

This requires nested lists concept.

Cf. the prototype.

Inputs


Outputs

  • String or expression
    image

  • Script
    image

  • List
    image

  • Map
    image

@pinussilvestrus
Copy link
Contributor

In case of camunda:inputOutput, only the first syntax error in an expression is reported by the engine; XML order matter

Source: #2 (comment)

Therefore we might consider disabling sorting here.

@pinussilvestrus
Copy link
Contributor

pinussilvestrus commented Sep 6, 2021

Inside the old properties panel, we created a first iteration of what we call "auto-suggest text component" - only used by input/output parameter expressions. The question for me would be whether we want to spend time rebuilding this thing. I'd vote for no and tackle it at a later point in time because

  • it was really just a first iteration and there is much room for improvement
  • it would take us time to build this "hack" again
  • it would take us more time right now to build a proper autocomplete (concept + implementation)
  • we plan to maybe have a proper code editor/syntax highlighting component anyway in the future (at least we had it once in our OKRs)
  • we don't know yet how much this single input was actually used

image


I've created an issue to have this once tracked: https://github.com/bpmn-io/bpmn-properties-panel/issues/98

@pinussilvestrus pinussilvestrus changed the title Migrate camunda:InputOutput group Implement inputs & outputs group Sep 6, 2021
pinussilvestrus pushed a commit to bpmn-io/properties-panel that referenced this issue Sep 7, 2021
@pinussilvestrus pinussilvestrus added this to the M50 milestone Sep 7, 2021
pinussilvestrus pushed a commit to camunda/camunda-bpmn-js that referenced this issue Sep 7, 2021
pinussilvestrus pushed a commit that referenced this issue Sep 9, 2021
pinussilvestrus pushed a commit that referenced this issue Sep 9, 2021
pinussilvestrus pushed a commit that referenced this issue Sep 9, 2021
pinussilvestrus pushed a commit that referenced this issue Sep 9, 2021
pinussilvestrus pushed a commit that referenced this issue Sep 9, 2021
pinussilvestrus pushed a commit to bpmn-io/properties-panel that referenced this issue Sep 10, 2021
pinussilvestrus pushed a commit that referenced this issue Sep 10, 2021
pinussilvestrus pushed a commit to bpmn-io/properties-panel that referenced this issue Sep 13, 2021
pinussilvestrus pushed a commit that referenced this issue Sep 13, 2021
pinussilvestrus pushed a commit to bpmn-io/properties-panel that referenced this issue Sep 13, 2021
pinussilvestrus pushed a commit that referenced this issue Sep 13, 2021
pinussilvestrus pushed a commit to bpmn-io/properties-panel that referenced this issue Sep 13, 2021
pinussilvestrus pushed a commit to bpmn-io/properties-panel that referenced this issue Sep 14, 2021
pinussilvestrus pushed a commit that referenced this issue Sep 14, 2021
pinussilvestrus pushed a commit to camunda/camunda-bpmn-js that referenced this issue Sep 14, 2021
pinussilvestrus pushed a commit to camunda/camunda-bpmn-js that referenced this issue Sep 14, 2021
pinussilvestrus pushed a commit that referenced this issue Sep 14, 2021
philippfromme pushed a commit to camunda/camunda-bpmn-js that referenced this issue Sep 15, 2021
MaxTru pushed a commit that referenced this issue Sep 15, 2021
@MaxTru MaxTru removed this from the M50 milestone Sep 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging a pull request may close this issue.

3 participants