This repository has been archived by the owner on Sep 6, 2019. It is now read-only.
forked from stoplightio/api-spec-converter
-
Notifications
You must be signed in to change notification settings - Fork 48
Issues: mulesoft/oas-raml-converter
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
ERROR ./node_modules/raml-1-parser/dist/parser/ast.core/expanderLL.js at compilation.
#60
opened Aug 28, 2019 by
n333ck
RAML 1.0 > OAS 3.0 not conforming to the spec when merging traits and resourceTypes
#59
opened Aug 4, 2019 by
p-bakker
RAML 1.0 to OAS 3.0 doesn't convert baseUriParameters default value
#56
opened Mar 27, 2019 by
gtrevg
In RAML 1 to OAS3 conversion, resource description should not be a lost semantic
#48
opened Aug 16, 2018 by
jsamr
In OAS3, converter should never use
$ref
at schema root since it prevents overriding metadata fields
#47
opened Aug 16, 2018 by
jsamr
In OAS30, converter should output all content types for one peculiar path
#44
opened Aug 2, 2018 by
jsamr
Wrong OAS30 object type definition which faultily inherits from string
#43
opened Aug 2, 2018 by
jsamr
Invalid conversion result when converting RAML 1.0 with multiple examples to OAS 2
#38
opened Jun 13, 2018 by
mduesterhoeft
raml array of objects in query parameters converts to array of string
#36
opened May 15, 2018 by
ricardomelocastro
RAML <<parm>> macro in traits are not supported when moveing to OAS2.0/OAS3.0
#30
opened Dec 20, 2017 by
fruch
Previous Next
ProTip!
Updated in the last three days: updated:>2024-11-09.