Is it Possible in RAML to skip a particular REST API Documentation in Spring Boot or it's not possible in RAML.

I'm seeing more and more raml2html themes on NPM, which is awesome! And also makes it painful that the process of writing themes is not documented anywhere. We provide the default theme and a Markdown theme which should be good examples to copy from, but that's about it.

1. Themes can provide index.js with their own config object (or a function that returns such config object)
2. Or they can

This issue related to the documentation, particularly to the README.md in this repository.

Steps to reproduce:

1. Scroll README to examples.
2. Click any example.

Actual behaviour:
Browser shows an access error from S3:

<Error>
  <Code>AccessDenied</Code>
  <Message>Ac

Hello,

Is there any documentation of this project somewhere else? The readme.md provided is not comprehensive / self-contained. The configuration effort for a new user is not that less and the documentation is not explanatory for this. One needs to check the actual implementation to understand what is actually meant and it is not always sufficient to get the things working.

Examples should be self contained and possible stored in a different repository. They way they are right now is confusing for final users as they need to detangle all the dependencyManagement, buildManagament and versioning for a multilevel multimodule project.

Hey all,

Just a comment that I think the Documentation tab (do you call this a tab, or a button?) should be re-named to "Description" as it will add a Description element to whatever node you are on and not a Documentation element. When I see "Documentation", I intuitively think this is going to add a Documentation node to the root of the RAML doc.

![image](https://cloud.githubusercontent.com

Ok case

If we have an example on an object type containing an array property, all is well :
When parsing the following.

/example:
  post:
    body:
      application/json:
        properties:
          arrayProperty:
            type: array
            items: string
        example:
          arrayProperty:
          - x
          - y

We get from the body example :

below link has all API interface but documentation and their usage of interface is not clear enough
https://raml-org.github.io/raml-js-parser-2/interfaces/_src_raml1_artifacts_raml10parserapi_.api.html#version

please provide some documentation to use the interface

Setup information
hikaku version: 2.0.0-SNAPSHOT
implementation converter: SpringConverter

Describe the bug
Spring data supports the idea of Pageable. A pageable is an object build by request parameter, supporting page, size and sort (parameter names are changeable). These par

Describe the bug
When adding a description to a path parameter, header, or query parameter in design view, the field displays improperly and cannot be used.

To Reproduce

1. Create a Path Parameter, Header, or Query Parameter in design view
2. Add a description by clicking the book icon

Expected behavior
A field appears that allows you to add a description.

**Screensh

The README is lacking quite a bit of detail to offer more examples and such of how to use raml-generator. It would be nice to show some content on how to use the handlebars templates, as well as using the RAML 1.0 JS parser to parse any RAML 1.0 document, how to navigate through libraries, types, and more.

When an example isn't valid JSON, the error you get looks like this:
AssertionError: Invalid JSON:
undefined
Error: expected [Function] to not throw an error but 'SyntaxError: Unexpected string' was thrown

Followed by a stack trace. It would be nice if:
a) the error identified that it was the example and not the json schema that was invalid.
b) the error provided more information about what

Lets put some more content.. a lot more in the README. I dont have a good idea of what this project does, why you would use it, examples of how to use it, etc. The README is the place for this sort of stuff (or at least links to examples, etc). The current README leaves a lot to be desired as to the purpose and use of this project.