Skip to content

Commit 7416a7a

Browse files
committed
go-script-bash v1.2.0
1 parent fb6f3ae commit 7416a7a

File tree

3 files changed

+14
-22
lines changed

3 files changed

+14
-22
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -195,8 +195,8 @@ scripts can be in any other interpreted language.__
195195
First you'll need a copy of this framework available in your project sources.
196196
Archives are available at:
197197

198-
- https://github.com/mbland/go-script-bash/archive/v1.1.2.tar.gz
199-
- https://github.com/mbland/go-script-bash/archive/v1.1.2.zip
198+
- https://github.com/mbland/go-script-bash/archive/v1.2.0.tar.gz
199+
- https://github.com/mbland/go-script-bash/archive/v1.2.0.zip
200200

201201
You can also add this repository to your project as a [`Git
202202
submodule`](https://git-scm.com/book/en/v2/Git-Tools-Submodules):

RELEASE.md

Lines changed: 11 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
# go-script-bash v1.1.2
1+
# go-script-bash v1.2.0
22

3-
This is a bugfix release.
3+
This release adds a stack trace feature to the public API.
44

55
## The `./go` script: a unified development environment interface
66

@@ -16,27 +16,19 @@ This software is made available as [Open Source software](https://opensource.org
1616

1717
## What's new in this release
1818

19-
### modules: Improved error handling for `. "$_GO_USE_MODULES"`
19+
### Print stack traces
2020

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.
2222

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)).
24-
25-
## Changes since v1.1.1
23+
## Changes since v1.1.2
2624

2725
<pre>
28-
22bace2 Mike Bland <[email protected]>
29-
Merge pull request #26 from mbland/module-import
30-
31-
8833762 Mike Bland <[email protected]>
32-
use: Improve module import error message
33-
34-
4bb94e2 Mike Bland <[email protected]>
35-
use: Nest module file path tests
26+
fb6f3ae Mike Bland <[email protected]>
27+
Merge pull request #27 from mbland/stack-trace
3628

37-
92bc468 Mike Bland <[email protected]>
38-
use: Detect module path before sourcing
29+
30790c9 Mike Bland <[email protected]>
30+
use: Show stack trace when an import fails
3931

40-
5ea7820 Mike Bland <[email protected]>
41-
modules: Fix incorrect help text
32+
8563f4d Mike Bland <[email protected]>
33+
core: Add @go.print_stack_trace to public API
4234
</pre>

go-core.bash

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ fi
3939
# This and other variables are exported, so that command scripts written in
4040
# languages other than Bash (and hence run in new processes) can access them.
4141
# See `./go vars` and `./go help vars`.
42-
declare -r -x _GO_CORE_VERSION='v1.1.2'
42+
declare -r -x _GO_CORE_VERSION='v1.2.0'
4343

4444
# The URL of the framework's original source repository
4545
declare -r -x _GO_CORE_URL='https://github.com/mbland/go-script-bash'

0 commit comments

Comments
 (0)