Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-778

Error highlighting doesn't work in the "Go" devfile

    XMLWordPrintable

Details

    • Hide
      • Go to dashboard and create a workspace using default "Go" devfile
      • Go inside workspace and open any "go" file
      • Wait until LS is started
      • Type in any row the next next "^&#@$"
      • Pay attention that error highlighting doesn't work, please notice that LS is started and for example autocomletion works.

      Show
      Go to dashboard and create a workspace using default "Go" devfile Go inside workspace and open any "go" file Wait until LS is started Type in any row the next next "^&#@$" Pay attention that error highlighting doesn't work, please notice that LS is started and for example autocomletion works.

    Description

      Error highlighting doesn't work in the "Go" devfile

      (Looks like fixed in upstream https://github.com/eclipse/che/issues/16113)

      Environment:

      • OCP cluster (3.11 , 4.3 , 4.4)
      • quay.io/crw/server-rhel8:2.1-19
      • quay.io/crw/devfileregistry-rhel8:2.1-61
      • quay.io/crw/pluginregistry-rhel8:2.1-78

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. CRW-779 Debugging of the current file failed to start in the "Go" devfile

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. CRW-1021 Failed to launch debug session in the "Go" devfile

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          QE Task - QE Task CRW-1019 The "Go to definition" function doesn't work in the "Go" workspace

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. CRW-774 Ensure 3rd party deps for stacks are available for multiple platforms

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Activity

            People

              vsvydenk Valerii Svydenko
              iokhrime Ihor Okhrimenko (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: