1.3.0

copied from openapi-processor-core

• openapi-processor/openapi-processor-core#30, preserve the "?" generic parameter of a mapping and pass it on to the generated api, e.g. a mapping like

  map:
    paths:
      /foo:
        parameters:
          - add: foo => io.openapiprocessor.Foo<?>

  does now generate

  void foo(Foo<?> foo);

  instead of

  void foo(Foo foo);

• openapi-processor/openapi-processor-spring#119, primitive type could match a primitive type with format mapping, e.g. with the mapping

  openapi-processor-spring: v2
  
  map:
    types:
      - type: string:binary => io.openapiprocessor.Foo
  

  it was possible that a primitive string was mapped to io.openapiprocessor.Foo instead of java.lang.String

• a ref loop with array items caused a NullPointerException

1.2.1

copied from openapi-processor-core

• the internal representation of an empty response (ie. without any response data) leaked to the generated code. Visible by a produces = {"?"} in the mapping annotation and an Object return type of the endpoint.

1.2.0

copied from openapi-processor-core

• add @NotNull if nullable is default (i.e. true) and bean validation is enabled.

• openapi-processor/openapi-processor-core#20, the type mapping (v2 only) configuration allows to reference the target package-name in generic parameters using the {package-name} expression. This makes it possible to adjust the package-name without touching the mapping and it can reduce duplication if the mapping contains many generic parameters.

  openapi-processor-mapping: v2
  options:
    package-name: io.openapiprocessor.generated.model
  
  map:
    types:
      - type: FooPage => org.springframework.data.domain.Page<{package-name}.Foo>
  

• openapi-processor/openapi-processor-core#21, a primitive type with a custom format (not defined by the OpenAPI specification) did break processing. The processor does now ignore unknown custom formats. For example the following definition

  type: string
  format: unknown-custom-format
  

  will be processed as if it has no format at all:

  type: string
  

• openapi-processor/openapi-processor-core#22, mapping of primitive schemas did not work. It is now possible to have a primitive schema

  components:
    schemas:
      Foo:
        type: string
  

  and map this to a specific target java type:

  openapi-processor-spring: v2
  
  map:
    types:
      - type: Foo => io.openapiprocessor.sample.Foo
  

• openapi-processor/openapi-processor-core#23, parameter $ref's were not resolved when processing with the openapi4j parser.

• updated openapi4j parser to 1.0.4 (was 1.0.3)

1.1.1

copied from openapi-processor-core

• fixed openapi-processor/openapi-processor-spring#116

1.1.0

copied from openapi-processor-core

• openapi-processor/openapi-processor-core#10, support for OpenAPI deprecated property at endpoint, parameter, schema and schema property level. It translates to @Deprecated annotations
• openapi-processor/openapi-processor-core#12, fix windows path/url handling, i.e. unknown protocol: c
• fix build on windows
• new model Endpoint method List<String> getConsumesContentTypes() that provides the list of consumeable media types. Helps to fix openapi-processor/openapi-processor-micronaut#1
• support path $ref (openapi4j)
• more tolerant mapping parser
• updated openapi4j parser to 1.0.3 (was 1.0.0)
• updated swagger parse to 2.0.21 (was 2.0.20)

1.0.0

copied from openapi-processor-core

• improved obsolete mapping/mapping key check
• updated openapi-processor-test

1.0.0.M2

copied from openapi-processor-core

• (openapi-processor/openapi-processor-core#2) renamed mapping.yaml version identifier from openapi-processor-spring to openapi-processor-mapping
• (openapi-processor/openapi-processor-core#4) updated openapi4j parser to 1.0.0
• (openapi-processor/openapi-processor-core#8) new group id: io.openapiprocessor
• new repository: https://dl.bintray.com/openapi-processor/primary

1.0.0.M1

copied from openapi-processor-core

• inital release, extracted from openapi-processor-spring 1.0.0.M15