New element creation through model browser #2585
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
marek-piirikivi
force-pushed
the
modelbrowser_element_creation
branch
from
7728e39
to
6a3fd7e
Compare
amolenaar
reviewed
Aug 3, 2023
marek-piirikivi
force-pushed
the
modelbrowser_element_creation
branch
from
6a3fd7e
to
d319989
Compare
marek-piirikivi
force-pushed
the
modelbrowser_element_creation
branch
from
d319989
to
e5945b9
Compare
danyeaw
added
feature
|
I love this feature, nice one @marek-piirikivi 🤩 |
|
Yup, works as expected. We may want to extend it at some point (e.g. create actions in activities), but that can be done later. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allows creating new elements directly in the model browser.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: #2552
What is the new behavior?
Does this PR introduce a breaking change?
Other information