shanedell commented on issue #1352:
URL:
https://github.com/apache/daffodil-vscode/issues/1352#issuecomment-3353789175
@stevedlawrence @mbeckerle Is there a good way you guys suggest we support
two different versions of our debugger, one using Daffodil 3 and one using 4? I
thought of mostly two ways:
1. Separate out the debugger code into a separate repository, such as
`daffodil-vscode-debugger`.
- With this we push up the current debugger code and create release of
it that will use Daffodil 3.11.4 and Scala 2.13. So maybe the release would
just be uploading the bin zip made from `sbt Universal/packageBin` with a name
something like
`daffodil-vscode-debugger-<scala-version>-<daffodil-version>.zip`. Once that is
released we can update the code to use Daffodil 4.0.0 and Scala 3, then which
we create another release, following same naming scheme.
- For the extension we could do something like, when debugging the
extension allow downloading the debugger directly from the internet to allow
for easier testing of the debugger version. But when we create a release of the
VSIX we have it either bundle just one versions of the debugger or both. In
either case we may want to allow the extension to be able to run both version
of the debugger, possibly adding a launch config setting that allows the user
to define which debugger version they want to use.
2. Create a separate folder in our repository and rename the current
`debugger` folder.
- So say we would have folders `debugger3` and `debugger4`
- `debugger3` holds the Daffodil 3 and Scala 2.13 code
- `debugger4` holds the Daffodil 4 and Scala 3 code.
- Then similar to the previous situation make the extension able to
either bundle with one or both of the debuggers and possibly also allow the
extension to let the user chose which version of the debugger they want to run
their specific debug instance with.
I think number 1 would make the debugging of the extension easier as then we
wouldn't be compiling all the Scala debugger code alongside all the typescript
extension code.
What do you guys think would be best? Maybe it would be helpful to what is
the path Daffodil is taking to support Daffodil 3 alongside 4?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
