Releases: apache/incubator-kie-tools
0.2.2 (alpha)
On this release:
- KOGITO-541: Format the output XML
- Dependency cleanup on
@kogito-tooling/*
NPM packages.
NOTE: To install new versions of the VSCode Extension, we recommend uninstalling any previous versions and restarting VSCode before doing so.
Known issues
- KOGITO-469: Fix disabled Save button on VSCode "File > Save" menu
- KOGITO-437: Stunner - Zoom widget duplicated after
setContent
calls. - KOGITO-342: Check why BPMN editor shows error on page closing.
- KOGITO-347: Error logs happening during BPMN marshalling.
- AF-2113 No indication of a modified BPMN diagram.
- AF-2168 No confirmation popup when closing a modified BPMN diagram.
- KOGITO-155 Flicker when opening or restoring editors.
- AF-2167 Native editor key bindings for macOS.
- AF-2113 No indication of a modified BPMN diagram.
- AF-2168 No confirmation popup when closing a modified BPMN diagram.
- KOGITO-157 Copy/paste between different BPMN diagram.
- KOGITO-224 An error message is displayed if you try to create a new type by pressing
Enter
. - KOGITO-225 Custom type definitions aren’t re-used within the diagram.
- KOGITO-272 Editor doesn't close when file is deleted.
0.2.1 (alpha)
This release contains some important internal changes to improve code quality and runtime performance. This is the first release where our packages are going to be released on NPM's public registry. That means you can build VSCode and Chrome extensions using our APIs. Stay tuned! 🎉
We also fixed a minor bug on GItHub's Chrome Extension. See KOGITO-483
NOTE: To install new versions of the VSCode Extension, we recommend uninstalling any previous versions and restarting VSCode before doing so.
Known issues
- KOGITO-469: Fix disabled Save button on VSCode "File > Save" menu
- KOGITO-437: Stunner - Zoom widget duplicated after
setContent
calls. - KOGITO-342: Check why BPMN editor shows error on page closing.
- KOGITO-347: Error logs happening during BPMN marshalling.
- AF-2113 No indication of a modified BPMN diagram.
- AF-2168 No confirmation popup when closing a modified BPMN diagram.
- KOGITO-155 Flicker when opening or restoring editors.
- AF-2167 Native editor key bindings for macOS.
- AF-2113 No indication of a modified BPMN diagram.
- AF-2168 No confirmation popup when closing a modified BPMN diagram.
- KOGITO-157 Copy/paste between different BPMN diagram.
- KOGITO-224 An error message is displayed if you try to create a new type by pressing
Enter
. - KOGITO-225 Custom type definitions aren’t re-used within the diagram.
- KOGITO-272 Editor doesn't close when file is deleted.
0.2.0 (alpha)
We are happy to announce a fresh Kogito Tooling alpha release that includes a major milestone for our team -- the DMN support for VSCode and GitHub Chrome extensions 🎉
VSCode Extension
From this release on, you'll be able to edit DMN files directly on VSCode just like you did with BPMN on the previous releases.
Features
- KOGITO-448: Configure extensions to support DMN files
- AF-2119: Integrate UX design of Loading Screen
Chrome Extension
We also added some important enhancements to our GitHub Chrome Extension. Now users will be able to not just edit but also visualize DMN/BPMN diagrams -- what is especially cool on Pull Request reviews as seen below.
Features
- AF-2274: Open editor on the assets of a PR to compare
- AF-2273: Open editor on visualization screen on GitHub
- KOGITO-448: Configure extensions to support DMN files
- AF-2119: Integrate UX design of Loading Screen
NOTE: When editing a file directly on GitHub's interface and committing it, GitHub takes a while to make the new file available on
raw.githubusercontent.com
. Since that's where we fetch the files from, you might see outdated versions for a while. Don't panic! After a few moments the files will be in sync.
Known issues
- KOGITO-469: Fix disabled Save button on VSCode "File > Save" menu
- KOGITO-437: Stunner - Zoom widget duplicated after
setContent
calls. - KOGITO-342: Check why BPMN editor shows error on page closing.
- KOGITO-347: Error logs happening during BPMN marshaling.
- AF-2113 No indication of a modified BPMN diagram.
- AF-2168 No confirmation popup when closing a modified BPMN diagram.
- KOGITO-155 Flicker when opening or restoring editors.
- AF-2167 Native editor key bindings for macOS.
- AF-2113 No indication of a modified BPMN diagram.
- AF-2168 No confirmation popup when closing a modified BPMN diagram.
- KOGITO-157 Copy/paste between different BPMN diagram.
- KOGITO-224 An error message is displayed if you try to create a new type by pressing
Enter
. - KOGITO-225 Custom type definitions aren’t re-used within the diagram.
- KOGITO-272 Editor doesn't close when file is deleted.
0.1.1 (alpha)
We are very happy to announce the second alpha release of Kogito Tooling!
This release features a new Chrome Extension that allows visualising and editing .bpmn
and .bpmn2
files directly on GitHub's interface 🎉
We also updated the VSCode extension with some important fixes. See details below.
Chrome Extension
Features
- Open and edit BPMN and BPMN2 files directly on GitHub's interface.
- Commit or propose file changes directly on GitHub's interface.
- Use keyboard shortcuts like Ctrl+Z (undo), Ctrl+C (copy), Ctrl+V (paste). Note that on macOS you have to use
Ctrl
too, and notCmmd
. We are working on fixing that on the next releases. - Use
Full screen
mode to edit large BPMN Diagrams. You can go back by clicking onExit full screen
at the top of the window. - When you're editing a BPMN diagram, you can click on
See as source
to edit the XML manually. You can always go back to the diagram by clicking onSee as diagram
.
Known issues
- KOGITO-342 Check why BPMN editor shows error on page closing.
- KOGITO-347 Error logs happening during marshalling
- AF-2167 Native editor key bindings for macOS.
VSCode Extension
Features and fixes
- KOGITO-286 Fix VSCode editor path issues on Windows.
- KOGITO-226 Not all BPMN constructs (elements) are supported. If a non-supported construct is used, an error message will be displayed.
- KOGITO-293 Fix client-side marshaller to work with unsupported elements roundtrip.
Known issues
- KOGITO-155 Flicker when opening or restoring editors.
- AF-2167 Native editor key bindings for macOS.
- AF-2113 No indication of a modified BPMN diagram.
- AF-2168 No confirmation popup when closing a modified BPMN diagram.
- KOGITO-157 Copy/paste between different BPMN diagram.
- KOGITO-224 An error message is displayed if you try to create a new type by pressing
Enter
. - KOGITO-225 Custom type definitions aren’t re-used within the diagram.
- KOGITO-272 Editor doesn't close when file is deleted.
0.1.0 (alpha)
We are really happy to announce the first alpha release of our VSCode extension -- the BPMN editor. This release marks the first piece of the new tooling infrastructure for the KIE Group Team.
Features
- Open and edit BPMN and BPMN2 files using the KIE Group BPMN editor.
- Save changes using built-in
Save
andSave All
commands. - Use keyboard shortcuts right on the BPMN editor like
Ctrl+Z
(undo),Ctrl+C
(copy),Ctrl+V
(paste). Note that on macOS you have to useCtrl
too, and notCmd
. We are working on fixing that on the next releases. - If a BPMN editor is already open but you want to see a file as text, you can right-click on this file and choose "Open to the side". VSCode editor will split in half and the file will open as text.
Known issues
- KOGITO-155 Flicker when opening or restoring editors.
- AF-2167 Native editor key bindings for macOS.
- AF-2113 No indication of a modified BPMN diagram..
- AF-2168 No confirmation popup when closing a modified BPMN diagram.
- KOGITO-157 Copy/paste between different BPMN diagram.
- KOGITO-224 An error message is displayed if you try to create a new type by pressing
Enter
. - KOGITO-225 Custom type definitions aren’t re-used within the diagram.
- KOGITO-226 Not all BPMN constructs (elements) are supported. If a non-supported construct is used, an error message will be displayed.
- KOGITO-272 Editor doesn't close when file is deleted.