-
Notifications
You must be signed in to change notification settings - Fork 488
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
Bump BPMN and DMN modeling dependencies / integrate implicit keyboard binding #4620
Conversation
This Pull Request targets Consider targeting |
Blockers:
Nice to have:
|
56ae8f1
to
8ed2972
Compare
b3f757a
to
a2ceba8
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
0eb28f0
to
7257234
Compare
Cleaned up git history. |
dirty, | ||
distribute: selectionLength > 2, | ||
editLabel: !inputActive && !!selectionLength, | ||
editLabel: canvasFocused && selectionLength === 1, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A good one!
Not a big problem, but when I click outside of the canvas (tab bar), some of the menu items are enabled but don't do anything: Screen.Recording.2024-11-21.at.10.05.30.mov |
SelectAll does not work in the BPMN properties panel. It works in DMN though. Screen.Recording.2024-11-21.at.10.11.31.mov |
Standard pattern when combining commits is:
You may want to account for that. Also, you may want to remove transient things, i.e. stuff that fixes behavior on top of existing contributions on this branch from the summary:
|
@@ -432,45 +434,46 @@ export class BpmnEditor extends CachedComponent { | |||
|
|||
const selectionLength = selection.get().length; | |||
|
|||
const inputActive = isInputActive(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is breaking for all plugins relying on inputActive. I'd say let's leave the state property as is, but the shortcuts don't need to rely on it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, as just discovered with @jarekdanielak, the getEditMenu
still depends on inputActive.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it had been, the properties panel select all wouldn't have broken #4620 (comment)
save: true, | ||
selectAll: true, | ||
selectAll: canvasFocused, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
selectAll: canvasFocused, | |
selectAll: canvasFocused || inputActive, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or we keep it as is, but adjust in the getEditMenu.
@@ -635,7 +617,6 @@ describe('<BpmnEditor>', function() { | |||
find: true, | |||
globalConnectTool: true, | |||
handTool: true, | |||
inputActive: false, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should still indicate inputActive
, right?
Related to bpmn-io/internal-docs#1081 feat: expose `canvasFocused` to menu actions This allows menu actions in plug-ins to properly react to the newly introduced canvas focused state, and make them activate only on canvas focus, not _any_ focus. fix: only trigger core editor keyboard shortcuts on canvas focus fix: focus canvas on attach This ensures that users can do modeling operations right away.
Makes the panel focusable. deps: bump to `[email protected]` Related to #4590
7257234
to
a1e415c
Compare
Brought back Fix git history once again. |
This commit contains a merge conflict in package-lock 86ddafa: 86ddafa#diff-053150b640a7ce75eff69d1a22cae7f0f94ad64ce9a855db544dda0929316519R41585 |
Besides the comment above, I believe the PR is ready to merge. We could squash the modeling deps updates to mitigate #4620 (comment) |
Makes the panel focusable, following along 23c9e6a.
a1e415c
to
a84b093
Compare
Fixed package-lock. Leaving it up to you how we want to squash dependencies updates together. @philippfromme can you give it a quick run on Windows? @nikku waiting for the final thumbs up and we can merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to have this wrapped up!
Proposed Changes
Updates BPMN and DMN modeling dependencies, integrating implicit keyboard / focusable canvas into the modeler application, but also addressing various other issues in the process.
Formal parameters suggestions are available without reloading:
Closes #4544
Closes #4684
Closes #4310
Work log
fixed upstream
issues that this closesChecklist
To ensure you provided everything we need to look at your PR:
@bpmn-io/sr
toolCloses {LINK_TO_ISSUE}
orRelated to {LINK_TO_ISSUE}
Try out via
better-actions
feature branch +npm run dev
, alternatively use this command:Child of https://github.com/bpmn-io/internal-docs/issues/1081