Skip to content

Releases: 72nd/osc-utility

v0.3.0 – General overhaul, consistent CLI, fewer dependencies

Choose a tag to compare

@72nd 72nd released this 08 Sep 10:02

A considerable amount of time has elapsed since the original version of osc-utility. Both the dependencies and Go itself have evolved significantly. With the new version v0.3.0, not only have the dependencies been updated, but they have been replaced with built-in packages wherever possible. Consequently, the external github.com/sirupsen/logrus is no longer utilised; instead, the native slog package is employed.

Furthermore, efforts have been made to design the CLI interface more consistently and to remove as much custom code as possible. Rather than using custom-implemented argument parsers, the functions from urfave/cli are now employed in almost all cases. The most significant change arising from this is that flags when sending OSC messages via osc-utility message no longer accept comma-separated values (--int 3,4), but instead require the flag to be used multiple times (--int 3 --int 4). Users who depend upon the legacy CLI interface may revert to version v0.2.2.

Additionally, a debug output can be activated using the global flag --debug. To improve the interoperability of osc-utility with other tools, output in JSON format can be enabled using the --json-log flag.

Changes

  • Dependency updates: urfave/cli to v3.4.1, go-osc to v0.0.0-20220308234300-cec5a8a1e5f5
  • Migration from logrus to built-in slog. Reduces the number of required external dependencies.
  • Debug output, optional log output in JSON format.
  • Consistent CLI interface: The port must always be explicitly set.
  • To send more than one value of the same type to a message via osc-utility message, the flag is now used multiple times.
  • Minor code refactoring.

v0.2.2 – Bug in the --int flag fixed

Choose a tag to compare

@72nd 72nd released this 06 Sep 11:29

The --int flag of the message command was marked in the code as an Int flag rather than a String flag. Fixed in #4 by @elModo7 Thanks! (Issue #5).

v0.2.1 – only send flags that were explicitly set

Choose a tag to compare

@72nd 72nd released this 16 Mar 20:51

Previously default values (at least for the --int flag) were always sent even when flags weren't specified. Now only transmits values that were explicitly set by the user.

v0.2.0 – Cross-platform build support & bug fixes

Choose a tag to compare

@72nd 72nd released this 16 Mar 16:01
  • Fixed CLI flag handling to resolve "flag redefined" panic error
  • Added Makefile for easy cross-platform builds (darwin, linux, windows)

v1.1.1

Choose a tag to compare

@72nd 72nd released this 28 Nov 21:06

Short flags fixed.

v1.1.0

Choose a tag to compare

@72nd 72nd released this 28 Nov 20:41
  • Moved to Github
  • Updated to cli v2
  • New project structure