Mike Beckerle provided some issues in 1.4.1-rc1, two of the issues were
considered blocking.
The first blocking issues has been resolved. The fix will be in 1.4.1-rc2.
Issue description:
(blocking) There is a real problem with "/" being typed. I know it is trying to
detect closing the element, but it has to be context sensitive since "/" is
such a common character to appear inside strings.
To reproduce, at the top level of the schema, try typing <xs:include
schemaLocation="/ I.e., a string that begins with a "/" character. The GUI
refuses to let you do this. It removes the quotation marks and anything you've
typed inside them.
<xs:include
schemaLocation="/org/apache/daffodil/xsd/DFDLGeneralFormat.dfdl.xsd"/>
<xs:annotation>
<xs:appinfo source="http://www.ogf.org/dfdl/";>
<dfdl:format ref="GeneralFormat"
representation="text" encoding="utf-8" lengthKind="delimited"/>
</xs:appinfo>
</xs:annotation>
The second blocking issue is not reproducible on most OSes, but it can be
reproduce on Ubuntu 20.04 LTS. It can not be reproduced on Ubuntu 22.04 LTS or
Ubuntu 24.04 LTS.
Issue decription:
(blocking) When I single step and the yellow cursor line moves down the "word"
element at line 25, the intellisense menu pulls down, as if I was typing in the
editor at that location. This is more than just distracting. We need a way to
tell the difference between the user editing and placing the cursor in a
location in order to edit, versus the debugger moving the position. The
intellisense should not respond to the debugger moving the current focus, only
to the user taking edit actions.
The issue occurs when utilizing the debugger to step through a schema in the
Ubuntu 20.04 OS. In the schema where this issue has been reproduced
(https://github.com/OpenDFDL/examples/blob/master/helloWorld/src/main/resources/helloWorld.dfdl.xsd),
when the debug focus gets to a line with an element that results in output to
the infoset, intellisense is triggered.
[cid:image003.jpg@01DAF910.E4735E90]
The intellisense triggered causes the display of an attribute items list for
the element on the line. I made a change to the code to prevent an
intellisense trigger from suggesting attribute items if the cursor was outside
of the element tag. When stepping through the schema after this change, the
dfdl extension didn’t suggest any intellisense items, but VS Code suggested a
default alphabetical list of words in the schema file when intellisense was
triggered.
[cid:image004.jpg@01DAF910.E4735E90]
Something is triggering intellisense when stepping through the schema file, but
so far it seems to do so only in Ubuntu 20.04 LTS. I can’t reproduce the issue
in Ubuntu 22.04 LTS or Ubuntu 24.04 LTS. I also cannot reproduce the issue in
Windows 10, Rocky 9 or Rhel 9. I can’t pinpoint a section of the typescript
code that is causing the trigger. Some of the debugger code is written in
Scala, but I can’t debug the scala code with the extension running the way I
can debug typescript code as it is running in VS Code.
Aside from these two issues, we have recorded the other issues that brought up
Mike Beckerle’s July 8 email and we have fixes many of them. Once a resolution
to the issue above is decided we will be releasing those fixes.
Mike Beckerle, I am wondering if it is absolutely necessary to resolve this
issue for Ubuntu 20.04 when it doesn’t occur in later releases? Let me know if
I should continue trying to track down what is causing debug stepping to
trigger intellisense in Ubuntu 20.04.
Rege
