Skip to content

Releases: bash-bastion/bash-core

v0.12.0

01 Dec 20:15
v0.12.0
d3e9eb2
Compare
Choose a tag to compare

Breaking Changes

Migrate to MPL-2.0 license

Features

  • Add convenience functions for IFS handling. (core.ifs_save to core.ifs_restore)
  • Fix lack of stderr indirection of some printfs
  • Deprecate print_die and print_die_fn functions

Fixes

  • Miscellaneous fixes

v0.11.0

30 Jul 19:58
v0.11.0
be02550
Compare
Choose a tag to compare

Features

  • Add core.print_die_fn()

Fixes

  • Informative messages are no longer printed erroneously to standard error (feaca30)

v0.10.2

14 Jul 18:49
v0.10.2
de0a960
Compare
Choose a tag to compare

Fixes

  • core.should_output_color() now calls the internal core.private.should_print_color() function for consistency
  • core.should_output_color() now accounts for FORCE_COLOR environment variable

v0.10.1

30 Jun 05:15
v0.10.1
e70960a
Compare
Choose a tag to compare

Fixes

  • Fix issue in which bash-core's trap handling function would be unset too soon
    • Previously, it would beunset after the first core.trap_remove for a particular signal (even if there are other user-provided handlers left). Now, it's only unset until after all user-provided handlers for a particular signal have been removed (with core.trap_remove)
    • The bug was introduced in this revision, when fixing the calculation of our trap handler function name
  • Fix unseting incorrect variables after certain loops

v0.10.0

30 Jun 03:39
v0.10.0
25ff1fb
Compare
Choose a tag to compare

Breaking Changes

  • core.print_die now executes the newly-added core.print_fatal instead of core.print_error

Features

New printing functions

  • core.print_{fatal,debug}?(_fn)

Fixes

  • Improve documentation wording

v0.9.0

25 Jun 20:20
v0.9.0
d973161
Compare
Choose a tag to compare

Breaking Changes

  1. When using core.print_*_fn functions, a set of parenthesis is now printed:

Example:

fnn() { core.print_info_fn 'Blah'; }
fnn

# Before:
# => Info: fnn: Something
# Now:
# => Info: fnn(): Something
  1. For core.print_{error,warn,info} parameterless calls no longer have special behavior
core.print_error

# Before:
# => Error
# Now:
# => Error: 

Features

  • Functions $core.print_(?:error|warn|info)(?:_fn)? functions now print color.
    • Color is properly suppressed if NO_COLOR is passed or if:
      • Either standard error (or stdout in the case of info) is not a terminal
      • Or $TERM is set to dumb

Miscellaneous

  • Documentation improvements
  • Prefix private methods with core.private.

v0.8.0

23 May 20:45
v0.8.0
94a522f
Compare
Choose a tag to compare

Features

  • Add core.print_die
  • Original core.print_* functions no longer show function name in output. New ones that still do have _fn postpended to them. These might be removed in the v1.0.0 release

Fixes

v0.7.1

06 May 20:44
v0.7.1
9d49281
Compare
Choose a tag to compare

Fixes

  • core.panic() properly prints stacktrace

v0.7.0

06 May 19:02
v0.7.0
0fc55a4
Compare
Choose a tag to compare

Features

  • Add core.panic()
    • Best used for programmer errors. It exit 1 while printing the applicable errors. Remember that you still need to account for subshells, etc.

Fixes

  • Fix regex in core.get_package_info so it actually works TOML files containing tabs

v0.6.0

12 Apr 03:15
v0.6.0
c9133ea
Compare
Choose a tag to compare

Features

  • New function core.print_error
  • New function core.print_warn
  • New function: core.print_info
  • New function core.print_stacktrace
    • Same exact functionality as previous core.stacktrace_print

Deprecations

  • Deprecate core.stacktrace_print
    • This was done so the naming was more consistent with the core.print_* family of functions. Expect this to be removed before the v1.0.0 stable release

Fixes

  • When printing errors, some functions incorrectly printed their own function names. This has been fixed
  • Miscellaneous documentation improvements