Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Print the absolute path of the file where a failure happens #20

Closed
mneumann opened this issue Sep 20, 2022 · 1 comment
Closed

Print the absolute path of the file where a failure happens #20

mneumann opened this issue Sep 20, 2022 · 1 comment

Comments

@mneumann
Copy link
Contributor

Extracted from #6
@mneumann mneumann mentioned this issue Sep 20, 2022
Closed
mneumann added a commit to mneumann/savi-Spec that referenced this issue Sep 22, 2022
@mneumann
Print root-package relative path of the file where a failure happens
91b8b3e 
Issue savi-lang#20 is about printing the absolute path and not the
package-relative path as this commit implements. We decided to use the
root-package relative path as the absolute path exposes details about
where you store your files and also makes the spec for `Spec` itself
difficult.

The root-package is the one where you are running `savi build` or `savi
run` from.

Related issues: savi-lang#20
@mneumann mneumann mentioned this issue Sep 22, 2022
Merged
mneumann added a commit that referenced this issue Sep 22, 2022
@mneumann
Print root-package relative path of the file where a failure happens (#…
f54fbed 
…22)

Issue #20 is about printing the absolute path and not the
package-relative path as this commit implements. We decided to use the
root-package relative path as the absolute path exposes details about
where you store your files and also makes the spec for `Spec` itself
difficult.

The root-package is the one where you are running `savi build` or `savi
run` from.

This requires savi v0.20220921.1 or later.

Related issues: #20
@mneumann
Copy link
Contributor Author

PR #22 prints root-package relative paths. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mneumann