This repository has been archived by the owner on Apr 1, 2022. It is now read-only.
WIP: Improve error messaging for invalid recipe files #101
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thank you for an excellent tool!
I recently had a problem that took some time to debug.
When running elinter locally, I had an emacs backup file in my
.recipes
directory:This was picked up when running elinter:
The
foo~
recipe pointed to a non-existent source file.The
copySource.nix
expression takes the head of the source files, aborting with the above out of bounds error if there are no source files:This took me a while to debug - I didn't realize that the error was thrown when processing the
foo~
recipeWhat do you think about adding a per-recipe logging statement?
This PR prints:
I'm marking this as a WIP while I figure out what's wrong with my
nixpkgs-fmt
hook. I assume that the hook shouldn't have reformatted the entirecopySources.nix
file.