I think of this as a daffodil server mode, for the front end VSCode stuff
to use.
So, is it plausable to add the code to daffodil proper. Make it a CLI
command mode to start up this server, so that
daffodil vscodeServer
starts it, optionally with connection options like what ports to use, etc.
On Tue, Jul 19, 2022 at 1:45 PM Shane Dell <shaned...@apache.org> wrote:
> All,
>
> This thread is to discuss splitting out the code for the Apache Daffodil
> Scala Debugger from the apache/daffodil-vscode repository. The two options
> would be:
>
> - 1.) Move the debugger source code into the apache/daffodil repo. However,
> will this work because the debugger code depends on certain daffodil Scala
> libraries to be published? This is mostly an option since both are
> mostly/fully Scala based.
> - 2.) Create a new repo (apache/daffodil-debugger?,
> apache/daffodil-debugger-scala?) where the Scala code will live.
>
> This would be helpful as the apache/daffodil-vscode repo is heavily based
> on creating the VS Code extension for Daffodil. With this the debugger
> source code is rarely updated, when it is they are pretty minor fixes or
> dependency updates. Currently it is a bit of a cluster having a mix of
> node/JavaScript/TypeScript and Scala which causes an issue with dependency
> bots checking as these are checking for both npm and sbt/Scala
> dependencies, causing many PRs to be made. The extension code also runs a
> sbt universal:packageBin command in multiple occurences, being able to
> remove this and downloading the debugger package would simplify a couple
> different processes for the extension.
>
> My personal vote is for creating a new repo called something like either
> apache/daffodil-debugger or apache/daffodil-debugger-scala.
>
> Sincerely,
>
> Shane Dell
>
