Wrap error from go/format as it is scanner.ErrorList #104
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.
Hi,
Using
jen
a lot lately (great project, btw). It was difficult to debug as the error is just a string with the resulting code which can be quite hard to figure out without doing properly formatting the resulting error.Since
go/format
returns a scanner.ErrorList error type, it would be nice to be able toerrors.As
to interact with the errors. This allow the code to be more like:Currently, I'm using my fork and this is the best I could come up with:
This would help the debugging experience, not perfect by any means.
Let me know what you think.
Not an expert on the matter so I would appreciate to know how others debug generated code 馃槃