Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-4399

BPMN/DMN assets changes can not be saved in VS Code extension

    XMLWordPrintable

Details

    • Bug
    • Status: Pull Request Sent (View Workflow)
    • Blocker
    • Resolution: Unresolved
    • Kogito Tooling 0.8.3
    • None
    • Authoring Tooling
    • None
    • Hide
      1. Create new DMN/BPMN file
      2. Add any node to the canvas
      3. Try to save
        1. File -> Save
        2. File -> Save as
        3. Ctlr + S
        4. Close asset -> Save in 'discard changes' pop-up

      Current: user is not able to save the file
      Expected user is able to save the file+

      Show
      Create new DMN/BPMN file Add any node to the canvas Try to save File -> Save File -> Save as Ctlr + S Close asset -> Save in 'discard changes' pop-up Current: user is not able to save the file Expected user is able to save the file+
    • ---
    • ---

    Description

      This issue was spotted on vsix extension built locally from master as yarn run build:prod

      • Menu items File -> Save, File -> Save as have no effect on the dirty status of the model.
      • Ctrl + s has no effect on the dirty status of the model
      • Closing dirty DMN model invokes a 'discard changes' pop-up, however if save is pressed, no effect, once such dialog is closed with cancel/save option pressed, the asset can not be closed at all

      Please notice, BPMN still can not be saved if there is a validation issue: KOGITO-4458

      Attachments

        Issue Links

          Activity

            People

              aparedes@redhat.com Adriel Paredes
              jomarko@redhat.com Jozef Marko
              Jozef Marko Jozef Marko
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: