We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.
The text was updated successfully, but these errors were encountered:
dependencies
Successfully merging a pull request may close this issue.
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.
The text was updated successfully, but these errors were encountered: