Skip to content

Conversation

mbland
Copy link
Owner

@mbland mbland commented Dec 13, 2016

Closes #25. Now any modules containing errors will be identified as such, rather than being reported as unknown.

Also contains a minor fix to the ./go help modules text.

cc: @JohnOmernik

Closes #25. Now any modules containing errors will be identified as
such, rather than being reported as unknown.
@coveralls
Copy link

Coverage Status

Coverage increased (+0.02%) to 95.084% when pulling bc16e46 on module-import into 2981cf2 on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.02%) to 95.084% when pulling 92bc468 on module-import into 2981cf2 on master.

It's slightly wasteful to keep issuing `-f "$__go_module_file"` checks
after finding a valid file path.
@coveralls
Copy link

Coverage Status

Coverage increased (+0.02%) to 95.084% when pulling 4bb94e2 on module-import into 2981cf2 on master.

It could be that the module has syntax errors, or that it failed to
define or import all its necessary functions and variables, or that it
deliberately raised an error based on an error condition. It's better to
state plainly that the import failed, and permit the user to ascertain
the cause from the module's output, rather than making it sound like the
module script is broken.
@coveralls
Copy link

Coverage Status

Coverage increased (+0.02%) to 95.084% when pulling 8833762 on module-import into 2981cf2 on master.

@mbland mbland merged commit 22bace2 into master Dec 13, 2016
@mbland mbland deleted the module-import branch December 13, 2016 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Better error checking in module loading
2 participants