Add 'init' command argument to set up configuration files #4
Conversation
Updated the logic in the autotest module to exclude the 'app' directory from the derived test path. This ensures that when files within the 'app' directory are modified, the corresponding test file's path is correctly identified, and the relevant tests are triggered.
Introduced a new command argument, 'init', to the CLI. When invoked, it automates the setup of the necessary configuration files for developers, streamlining the initial setup process and ensuring a consistent configuration across different development environments. This enhancement aims to simplify onboarding for new developers and reduce the initial setup time, promoting a smoother integration into their development workflows.
|
@davidjrice still a few things to clean up here like: String usage over list for those Src, tests etc where it will take either. I’ll support a list if the user has multiple items entered but by default it should be a string. I think that’s how toml works from my limited understanding. Some validation of what the user is imputing path wise would be nice eventually but it’s been the bane of my existence at 1am for too many nights in a row already (the grand total of 0) so for now I’m thinking it might be worth having a wee check after 30 seconds of running the command whether the user has successfully been able to run any tests at all and if not give them a polite link to refer to how to fix their TOML files. Adding init files to the tests folder |
1 participant
Introduced a new command argument, 'init', to the CLI. When invoked, it automates the setup of the necessary configuration files for developers, streamlining the initial setup process and ensuring a consistent configuration across different development environments.
This enhancement aims to simplify onboarding for new developers and reduce the initial setup time, promoting a smoother integration into their development workflows.