Skip to content

Releases: carueda/tscfg

size-in-bytes now supported

03 Feb 21:20
Compare
Choose a tag to compare

resolve #23 "support size-in-bytes type"

fix and code cleanup

19 Dec 19:46
Compare
Choose a tag to compare
  • fix issue #22 "literal duration captured as string"
  • code cleanup: generate code as part of test phase

some more adjustments

15 Dec 00:15
Compare
Choose a tag to compare

Some minor bug fixes; simplified generated code and additional tests

implementation rewrite and simplification

13 Dec 04:48
Compare
Choose a tag to compare

Code simplified, more consistent and better organized. All tests reviewed and coverage further increased (to 95%).

Some minor adjustments post 0.5.0 ; )

01 Dec 21:40
Compare
Choose a tag to compare

including some internal code cleanup

Now with support for lists, optional objects, lists; improved implementation

01 Dec 04:45
Compare
Choose a tag to compare

This is almost a complete rewrite of the tool! Thanks to that, now supporting lists, optional objects (sections), and hopeful making easier to further extend the tool later on.

  • resolve #16 "rewrite code"
  • resolve #15 "support list"
  • resolve #10 "annotations" -- basically only the #@optional one
  • NOTE: toString not generated anymore

some fixes and additions

16 Oct 20:17
Compare
Choose a tag to compare
  • fix #13 "scala: double definition"
    add build auxiliary method to avoid type erasure issue in case of optional member
  • --noToString now processed for scala
  • add options --toPropString and --noToString (only processed for java):
    • --toPropString to generate toPropString method (not generated by default)
    • --noToString to not generate toString method (generated by default)
  • fix #12 "incorrect reference with standard types in path fragments"
  • java: factor out access to Config parameter for sub-section in static method __$config at the root class
  • in java's toString, no need for conditional for string field if required or with default (non-null) value
  • allow missing sections in given input configuration.
    This helps with sections whose all members are optional.
    Still to be done is proper handling of optional sections in general. Besides an explicit annotation
    to indicate that a section is optional, note that a section can also be implicitly optional
    if all its members are optional.
  • fix #11 "name collision with no-arg methods in scope"

Minor changes

16 Aug 06:15
Compare
Choose a tag to compare
v0.3.1

fix in generated Scala's toString

Durations and templates

02 Mar 08:41
Compare
Choose a tag to compare

Implements #8 (support for durations, see readme) and #6 (generation of config templates)

fix #5

07 Feb 22:30
Compare
Choose a tag to compare

So, having "config" as fragment of any configuration path is now properly handled.