Skip to content

Commit

Permalink
go-script-bash v1.2.0
Browse files Browse the repository at this point in the history
  • Loading branch information
mbland committed Dec 14, 2016
1 parent fb6f3ae commit 7416a7a
Show file tree
Hide file tree
Showing 3 changed files with 14 additions and 22 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -195,8 +195,8 @@ scripts can be in any other interpreted language.__
First you'll need a copy of this framework available in your project sources.
Archives are available at:

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

You can also add this repository to your project as a [`Git
submodule`](https://git-scm.com/book/en/v2/Git-Tools-Submodules):
Expand Down
30 changes: 11 additions & 19 deletions RELEASE.md
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

Expand All @@ -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>
2 changes: 1 addition & 1 deletion go-core.bash
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ fi
# This and other variables are exported, so that command scripts written in
# languages other than Bash (and hence run in new processes) can access them.
# See `./go vars` and `./go help vars`.
declare -r -x _GO_CORE_VERSION='v1.1.2'
declare -r -x _GO_CORE_VERSION='v1.2.0'

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

0 comments on commit 7416a7a

Please sign in to comment.