You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This release adds a stack trace feature to the public API.
4
4
5
5
## The `./go` script: a unified development environment interface
6
6
@@ -16,27 +16,19 @@ This software is made available as [Open Source software](https://opensource.org
16
16
17
17
## What's new in this release
18
18
19
-
### modules: Improved error handling for `. "$_GO_USE_MODULES"`
19
+
### Print stack traces
20
20
21
-
Previously, the `$_GO_USE_MODULES` script would report an `Unknown module:` error in every error case, even if the module existed but failed for another reason ([Issue #25](https://github.com/mbland/go-script-bash/issues/25)). The module's standard error would also get redirected to `/dev/null`, which made diagnosis even more difficult.
21
+
The `@go.print_stack_trace` function is now part of the public API. Its original use case was to provide more helpful error messages from `. "$_GO_USE_MODULES"`, but it's generally useful. See the function comments in `go-core.bash` and `./go test --edit core/print-stack-trace` for more information.
22
22
23
-
Now any modules that actually exist but return an error when imported will be identified as such, rather than being reported as unknown, and standard error isn't redirected at all ([PR #26](https://github.com/mbland/go-script-bash/pull/26)).
0 commit comments