raml-java-parser icon indicating copy to clipboard operation
raml-java-parser copied to clipboard

(deprecated) A RAML parser based on SnakeYAML written in Java

Results 100 raml-java-parser issues
Sort by recently updated
recently updated
newest added

Hi guys, I have found this while working with raml-for-jaxrs examples: when I am parsing following raml: ``` raml #%RAML 1.0 --- title: "Muse: Mule Sales Enablement API" version: v1...

spec-question

``` raml #%RAML 1.0 title: hello securitySchemes: oauth2.0: type: OAuth 2.0 settings: authorizationGrants: password authorizationUri: http accessTokenUri: http scopes: - a - b /persons: get: securedBy: oauth2.0: scopes: - c...

spec-question

Hello, **Affects: 1.0.0** **Issue** Validations cannot be performed, returning the error: `Error validating Schema. Error: src-resolve: Cannot resolve the name 'tns:Personnage' to 'type definition' component.` **How to reproduce** person.xsd ```...

bug
v2

I'm not sure if this should be just a question or a feature request. I tried to find answers in the source code and by reading through existing issues here,...

enhancement
v2
minor

The example from the [spec](https://github.com/raml-org/raml-spec/blob/master/versions/raml-08/raml-08.md#user-content-named-parameters-with-multiple-types) gives 2 ValidationResults: ``` Invalid element { type: string, description: Text content. The text content must be the last field in the form. }. Invalid...

bug
v2
RAML 0.8

RAML 0.8 specification (https://github.com/raml-org/raml-spec/blob/master/versions/raml-08/raml-08.md#optional-properties) allows to append a question mark ("?") suffix to the name of any non-scalar property to define it as optional in traits and types. But currently...

bug
v2
minor
RAML 0.8

I have a RAML (v0.8) with reference to schema in the traits something like below `body: application/json: example: | { "error": { "originalMsgCode": "", "originalMsgText": "" } } schema: errorSchema`...

v2
RAML 0.8

When parsing valid 1.0 RAML with passing parameters, there is a parser error E.g. Resource type library with parameters defined ```yaml #%RAML 1.0 Library usage: Standard resourceTypes uses: standardTraits: ../traits/standardTraits.raml...

v2
RAML 1.0
selected

I want to parse raml and want to create client call. I am not sure end user will use it with version V08 or V10 raml format. Now for both...

# Ok case If we have an example on an object type containing an array property, all is well : When parsing the following. ```yaml /example: post: body: application/json: properties:...