-
Notifications
You must be signed in to change notification settings - Fork 109
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
Playground components are freely attachable and detachable #292
Labels
Comments
bpmn-io-tasks
bot
added
in progress
Currently worked on
and removed
ready
Ready to be worked on
labels
Jul 28, 2022
To test out the flexibility, I am currently creating a little prototype via https://github.com/pinussilvestrus/form-playground-prototypes/tree/attachable-components. |
Merged
pinussilvestrus
pushed a commit
that referenced
this issue
Aug 4, 2022
pinussilvestrus
pushed a commit
that referenced
this issue
Aug 4, 2022
pinussilvestrus
pushed a commit
that referenced
this issue
Aug 5, 2022
pinussilvestrus
pushed a commit
that referenced
this issue
Aug 5, 2022
pinussilvestrus
pushed a commit
that referenced
this issue
Aug 22, 2022
pinussilvestrus
pushed a commit
that referenced
this issue
Aug 23, 2022
bpmn-io-tasks
bot
added
needs review
Review pending
and removed
in progress
Currently worked on
labels
Aug 23, 2022
pinussilvestrus
pushed a commit
that referenced
this issue
Aug 23, 2022
pinussilvestrus
pushed a commit
that referenced
this issue
Aug 25, 2022
bpmn-io-tasks
bot
added
in progress
Currently worked on
and removed
needs review
Review pending
labels
Aug 29, 2022
pinussilvestrus
pushed a commit
that referenced
this issue
Aug 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What should we do?
In order to make the playground components flexible, they need to be freely attachable and detachable (as other components, e.g. properties panel, palette, editor, viewer).
This was already spiked via #253.
Why should we do it?
Child of https://github.com/bpmn-io/internal-docs/issues/527
The text was updated successfully, but these errors were encountered: