-
Notifications
You must be signed in to change notification settings - Fork 16
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
14 additions
and
22 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
# go-script-bash v1.1.2 | ||
# go-script-bash v1.2.0 | ||
|
||
This is a bugfix release. | ||
This release adds a stack trace feature to the public API. | ||
|
||
## The `./go` script: a unified development environment interface | ||
|
||
|
@@ -16,27 +16,19 @@ This software is made available as [Open Source software](https://opensource.org | |
|
||
## What's new in this release | ||
|
||
### modules: Improved error handling for `. "$_GO_USE_MODULES"` | ||
### Print stack traces | ||
|
||
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. | ||
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. | ||
|
||
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)). | ||
|
||
## Changes since v1.1.1 | ||
## Changes since v1.1.2 | ||
|
||
<pre> | ||
22bace2 Mike Bland <[email protected]> | ||
Merge pull request #26 from mbland/module-import | ||
|
||
8833762 Mike Bland <[email protected]> | ||
use: Improve module import error message | ||
|
||
4bb94e2 Mike Bland <[email protected]> | ||
use: Nest module file path tests | ||
fb6f3ae Mike Bland <[email protected]> | ||
Merge pull request #27 from mbland/stack-trace | ||
|
||
92bc468 Mike Bland <[email protected]> | ||
use: Detect module path before sourcing | ||
30790c9 Mike Bland <[email protected]> | ||
use: Show stack trace when an import fails | ||
|
||
5ea7820 Mike Bland <[email protected]> | ||
modules: Fix incorrect help text | ||
8563f4d Mike Bland <[email protected]> | ||
core: Add @go.print_stack_trace to public API | ||
</pre> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters