-
-
Notifications
You must be signed in to change notification settings - Fork 159
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
[bug] $projectRoot
is rendered with a leading tilde
#888
Comments
@shellscape The logs always replace the home dir with ~. Is this actually happening when the task is executed? |
yeah I added some logging to Ava's source and it was receiving the tilde |
@shellscape I can't seem to reproduce this 🤔 tasks:
tilde:
command: 'echo "$projectRoot"'
Tried it via node also: tasks:
tilde2:
command:
- node
- '-e'
- console.log("$projectRoot")
platform: 'node'
|
Super weird. I'll nuke a few things and see if I can track down the cause. Update 6/6: I have suspicions. Will be able to dive this deeper tomorrow. |
@shellscape Did you ever figure this out? |
not as yet. traveling this week so I'm on pause. |
Closing this. Let me know if it's still a problem in v1.11. |
Will do. We're upgrading later this week. |
Describe the bug
The
$projectRoot
variable is being rendered with a leading tilde (~) when interpolated. This is causing issues with third parties which do not automatically expand paths. (e.g. most node package CLIs)Using bash to expand the result is yielding a negative DX as it requires changing the paradigm of how the task command is constructed.
Steps to reproduce
Using a moon task:
Yields:
Update: I upgraded to 1.7.1 to see if that had an effect and it looks like there's some more info, but the same bug:
Note that the
MOON_PROJECT_ROOT
environment variable is correct but the interpolation result is not.Expected behavior
I expected moon to render
Users/user/code/test/services/svc-test
As an aside; it would be very helpful and useful if the release notes could list the actual things fixed, and link back to their respective PRs/commits. I had looked there before opening this bug and couldn't determine quickly if it had already been addressed in 1.7.1.
Screenshots
n/a
Environment
Additional context
The text was updated successfully, but these errors were encountered: