You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When generating a new field-guide, the default config for name, copyright, and github could all be inferred from existing files in the project. For example, the default name can be read from the name property in package.json, the github property can come from repository in package.json, and copyright could be pulled from COPYRIGHT.md. Instead of providing defaults we know will have to be changed, we could proactively provide intelligent defaults that may not need changing!
The text was updated successfully, but these errors were encountered:
I think it would be worthwhile just assuming that the files you're talking are available in process.cwd() but we should fall back sensibly if they are missing for some reason i.e. if the smart behaviour fails for whatever reason we have the same functionality as today 👍
When generating a new field-guide, the default config for
name
,copyright
, andgithub
could all be inferred from existing files in the project. For example, the defaultname
can be read from thename
property inpackage.json
, thegithub
property can come fromrepository
inpackage.json
, andcopyright
could be pulled fromCOPYRIGHT.md
. Instead of providing defaults we know will have to be changed, we could proactively provide intelligent defaults that may not need changing!The text was updated successfully, but these errors were encountered: