Api-workbench 0.8.24 horribly broken


#1

This does not work in api-workbench 0.8.24 and it worked fine in 0.8.23

#%RAML 1.0
mediaType: application/json
title: Test RAML
types:
  base:
    description: base class
    type: object
    properties:
      extensions:
        type: string[]
        required: false

  myType:
    type: base
    properties:
      myProperty:
        type: string
        required: true
    example:
      {
        "myProperty" : "somevalue"
      }

base.extensions.required:false is being ignored, making it a required property in the example.

Please check out the attached screenshot. Something is wrong with extensions’ attributes and properties. What is null marked in red???


#2

The problem seems to be even worse. This string[] is not working for some reason. If I just put extensions?:string it works, but if it’s a array it doesn’t.

#%RAML 1.0
mediaType: application/json
title: Test RAML
types:
  base:
    description: base class
    type: object
    properties:
      extensions?: string[]

#3

This doesn’t work either. error is “specifying unknown facet:format”

  myFloat:
    type: number
    format: float

#4

Hi @rojocapo, thanks for your report. The last with format has already been addressed inside the parser. For the first two, I have created separate issues for the parser and workbench.

We are investigating what the problem is and fixing it asap.


#5

Update: The issue #119 is fixed in the 0.2.3 version of the JS parser already. The changes will be visible inside the workbench with the release tomorrow.


#6

Hi Christian,

Thanks for opening both tickets in github and following up on these issues.

Regards
Axel


#7

I updated to 0.8.26. These issues have been fixed.