Shanedell commented on PR #224: URL: https://github.com/apache/daffodil-vscode/pull/224#issuecomment-1188484979
@stevedlawrence @mbeckerle Would there be any benefit to moving the Scala daffodil-debugger to its own repo, or possibly inside of daffodil? Would putting it in daffodil work since it depends on certain Scala libraries from daffodil to be published already? My personal vote would be a separate repo and we download the debugger server in a similar fashion to how we do with omega-edit. Also I prefer this as a lot of updates/issues dealt with in this repo are heavily geared toward the extension and the debugger does not get updated that often so might be best to have it in a standalone repo. This would help reduce the number of bot entries for this project since currently the bots check for updates to github-actions, npm and scala. Splitting out the scala side would allow this repo to focused solely on the VS Code extension. Also the complete build of VSIX file should be faster has we wouldn't be running `sbt universal:packageBin` anymroe. But with npm there is constantly going to update to packages, so it might be a good idea to have the bot check only once a month and limit the amount of PR it can open or only create a PR for security updates not just minor items. -- 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]
