Skip to content

Releases: Amartus/LsoBlendingTool

Release 1.9.3

08 Dec 21:24
Compare
Choose a tag to compare

Commits

  • b02bb4e: redefine build job (Bartosz Michalik)
  • b06775c: maintenance release (Bartosz Michalik)
  • 5935d62: script fix (Bartosz Michalik)

Release 1.9.2

23 Nov 13:42
Compare
Choose a tag to compare

Dependencies update for OAS parser and logging.

Full Changelog: v1.9.1...v1.9.2

Version 1.9

22 Aug 14:10
Compare
Choose a tag to compare

Added ability to generate default oauth based security definition for all paths in the API.
Upgrade of dependencies

Full Changelog: v1.8.0...v1.9

Version 1.8

18 Jun 13:11
Compare
Choose a tag to compare

Most important changes

  • new command merge - which allows to generate a minimal OAS with selected product / service schemas
  • version preserves descriptions even if they are provided next to $ref

Full Changelog: v1.7.2...v1.8.0

Version 1.7.1

19 Mar 22:54
Compare
Choose a tag to compare

Full Changelog: v1.6...v1.7.1

Version 1.6

26 Nov 13:18
Compare
Choose a tag to compare

Most important changes

  • automatically introduce enum value constrains into discriminator property (closes #5)
  • support for absolute and relative (to the value of -d property) paths for blended schemas

Version 1.5

07 Jun 22:25
Compare
Choose a tag to compare
  • User input validation improvements
  • Error message improvements
  • Alias for product (or service) schemas -b

Version 1.4

01 May 11:45
Compare
Choose a tag to compare

Version 1.4 improvements:

  • enables multi-file schema
  • adds blender parameter that allows for sorted types in output --sorted
  • improves multi-line text readability wherever possible

Version 1.3

25 Jan 17:32
Compare
Choose a tag to compare
  • closes #1
  • adds additional helper parameters to CLI

Version 1.2

14 Dec 14:01
Compare
Choose a tag to compare

Version 1.2 improvements:

  • added new parameter to point to the root product schemas directory (default to ".")
  • modified naming generation strategy for uplifted properties:
    • in case the uplifted property is a composed schema we try first to compute name from aggregated references (allOf and oneOf are supported)
    • if above fails name is based on property
  • modified behavior of uplifting schemas in case of composed schemas -> schema reuse if possible
  • discriminator mapping feature:
    • using x-discriminator-value
    • using $id value if it is MEF urn
    • using name of the type
  • discriminator discovery feature:
    • in case discriminator is not provided x-discriminator-name value is used
    • if above fails auto-discovery strategy of discriminator property is applied trying names from list (@type, mapType)
  • discriminator value mapping for schemas with singleton enums (enums containing single value)