cljacoby / pyproj

A CLI for python projects
MIT License
0 stars 0 forks source link

Assess whether or not to use a .pyproj configuration file #7

Open cljacoby opened 4 years ago

cljacoby commented 4 years ago

At the moment, it doesn't seem like a configuration file is necessary. However, adding a configuration file would allow introducing subcommands to operate on an existing project. I'm not sure of I'll put any of these in, and whether or not therefore using a configuration file makes sense.

cljacoby commented 4 years ago

As a secondary concern, a configuration file might make testing easier. If you can verify individual functionalities are accurately reflected in the configuration file, then advanced functionality, or composition of functionalities can be easily checked against the config file, rather than looking through the file system.

cljacoby commented 4 years ago

I also thought of adding .exists() and .remove() methods on the PyProj struct. As of yet, these aren't really needed, but would be easier to implement with a config file.