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

Add more diagnostic support #39

Open
jmgilman opened this issue Jul 21, 2022 · 0 comments
Open

Add more diagnostic support #39

jmgilman opened this issue Jul 21, 2022 · 0 comments
Assignees
@jmgilman
Labels
Effort: 3 Priority: High This issue is prioritized as high Status: Accepted This issue has been accepted Type: Feature This issue targets a new feature

Comments

@jmgilman
Copy link
Collaborator

Shaving away some of the mystery behind what Nixago is doing would be helpful.

  • Where is the generated file in the store?
  • What was the original input given? This may be dynamically generated and it can be helpful to see the final result.
  • Is the output supposed to be symlinked or a local copy?

The idea is to support easier troubleshooting in the event that Nixago produces something that doesn't make sense.
@jmgilman jmgilman added Status: Accepted This issue has been accepted Type: Feature This issue targets a new feature Priority: High This issue is prioritized as high Effort: 3 labels Jul 21, 2022
@jmgilman jmgilman self-assigned this Jul 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jmgilman jmgilman

Labels
Effort: 3 Priority: High This issue is prioritized as high Status: Accepted This issue has been accepted Type: Feature This issue targets a new feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jmgilman