Closed jbrunton closed 3 years ago
Currently we have:
Option A:
lib
workflows/
libs/
.gflowslib
.gflowspkg
Option B:
libs
paths
Option C:
packages
templates: engine: ytt libs: - vendor dependencies: - https://example.com/my-lib
Also consider: standardize package manifests on gflowspkg.json (or gflowslib.json, or gflows.pkg.json).
gflowspkg.json
gflowslib.json
gflows.pkg.json
Pros of A: naming consistent with packages in NPM ecosystem and others. Pros of C: simplify code and intent.
Currently we have:
Option A:
lib
to be any dependency (file, dir or package) added to the build pathworkflows/
andlibs/
directories..gflowslib
to.gflowspkg
?Option B:
libs
config option topaths
Option C:
packages
andlibs
(orpaths
) in config.Also consider: standardize package manifests on
gflowspkg.json
(orgflowslib.json
, orgflows.pkg.json
).Pros of A: naming consistent with packages in NPM ecosystem and others. Pros of C: simplify code and intent.