Enumeration schema inlined in OpenAPI YAML instead of declared and referenced

[middlewareman]

I have a simple enumeration like this:

sealed trait Outcome extends EnumEntry with Uppercase 

object Outcome extends Enum[Outcome] {
  case object Approved extends Outcome
  case object Denied extends Outcome
  case object Review extends Outcome
  case object Cancelled extends Outcome

  override val values: IndexedSeq[Outcome] = findValues

  def apply(name: String): Outcome = withNameInsensitive(name)

  implicit val decoder: Decoder[Outcome] = Decoder.decodeString map withNameInsensitive
  implicit val encoder: Encoder[Outcome] = Encoder.encodeString contramap (_.entryName)
}

In the generated OpenAPI document, the type is inlined as follows:

components:
  schemas:
    Activity:
      type: object
      properties:
        code:
          type: string
        decision:
          type: string
          enum:
          - APPROVED
          - DENIED
          - REVIEW
          - CANCELLED
    LogEntry:
      required:
      - decision
      - user
      type: object
      properties:
        user:
          type: string
        decision:
          type: string
          enum:
          - APPROVED
          - DENIED
          - REVIEW
          - CANCELLED

How can I instead make it its own type, as follows, without wrapping it in another case class?

components:
  schemas:
    Outcome:
      type: string
      enum:
        - APPROVED
        - DENIED
        - REVIEW
        - CANCELLED
    Activity:
      type: object
      properties:
        code:
          type: string
        decision:
          $ref: '#/components/schemas/Outcome'
    LogEntry:
      required:
      - decision
      - user
      type: object
      properties:
        user:
          type: string
        decision:
          $ref: '#/components/schemas/Outcome'

[pjfanning]

@middlewareman this is the line that adds it as an inline type - https://github.com/swagger-akka-http/swagger-enumeratum-module/blob/main/src/main/scala/com/github/swagger/enumeratum/converter/SwaggerEnumeratumModelConverter.scala#L21

feel free to fork this project and change the way this is done

I'm not really doing much with this project right now - don't use it myself and there are few if any other users

[pjfanning]

The existing behaviour is consistent with https://github.com/swagger-akka-http/swagger-scala-module (in the way it handles scala 2 enumerations). I see no reason to support a change. This existing behaviour is a valid way to represent enums in Open API spec.