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
Make use of the word “output” less confusing. Currently in specs.json we have:
specs.json
1:
"output_path": "./docs"
So the output path can be configured to a name to your liking (as long as it does not exist in the root dir)
"output_path" has variables created from that entry with “output” in them.
2:
At the same time we have a “system directory” that is called output/ (not configurable), where all files created by the Node.js scripts are saved.
output/
==> This is confusing, one of the two has to change. Preferably output/, to something better, like system-generated/
system-generated/
The text was updated successfully, but these errors were encountered:
Search for the following in the code base: output path outputPath
New strings will be added.
Sorry, something went wrong.
kordwarshuis
No branches or pull requests
Make use of the word “output” less confusing. Currently in
specs.json
we have:1:
So the output path can be configured to a name to your liking (as long as it does not exist in the root dir)
"output_path" has variables created from that entry with “output” in them.
2:
At the same time we have a “system directory” that is called
output/
(not configurable), where all files created by the Node.js scripts are saved.==>
This is confusing, one of the two has to change.
Preferably
output/
, to something better, likesystem-generated/
The text was updated successfully, but these errors were encountered: