Suggestion: launch.json

[teofanis]

Would you be open for an optional VS Code setting available during setup ?

Scenario :
User runs npx aocrunner init and is presented with the setup wizard.
After the user has selected their language, package manager, folder, name etc... an optional question is asked:
Would you like to enable VS Code integration/launch.json settings ? (y/N). (Or something similar)

If the user specifies "Y", a new .vscode/launch.json file will be added.

This will allow the user to press (F5/Ctrl+F5) or select Run and have VS Code prompt them for the number of the day they want to run.

(Example picture below)

Let me know if you'd be open to something like this and I can open a PR.

[caderek]

I don't know, on one side I like that the runner is IDE-agnostic (and npm start <day number> is imo simple enough), on the other side most people probably use VSCode anyway, and generating lunch.json could be a nice addition (especially if there is also a debugger config). I have to think about it. Is it worth implementing and pay the cost of maintaining?

[teofanis]

I agree, the runner should be IDE-agnostic, that's why I was thinking to prompt the user and let them decide during setup, whether to have "VS Code Run Integration" enabled or not.

As for maintenance, I don't think there will be any - The launch.json will call "npm"/"yarn"/"pnpm" (start) with an argument and the script will be doing the rest as it does today.

The way I see it, is that if the user wants it during setup, it will set some nice "defaults" that they can built upon, if they want to further customise what happens when they run it.