-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
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
feature-request: Interpret env name as inline if directory can't be found #636
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Bump to drop stale. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Bump to drop stale |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Bump to drop stale |
#637 merged! |
My Tanka workflow has led to extensive use of inline environments for various reasons.
One quality of life improvement would be not to need to type
tk --name <env_name> main.jsonnet
but rathertk <env_name>
again like can be done with non-inline/traditional environment setup withspec.json
.I did a quick PoC of this by detecting when the path doesn't exist, falling back to the current directory as the basedir and setting name to be the non-existent path.
This works but probably needs more thought put into UX and edge cases, patch is tiny and works in the cases I wanted it to: https://github.com/josephglanville/tanka/tree/jpg/fallback-inline
The text was updated successfully, but these errors were encountered: