When I try to install as follows:

go get gopkg.in/raml.v0

I get:

# github.com/advance512/yaml
../Dropbox/Development/go/src/github.com/advance512/yaml/error.go:4: "ERROR: the correct import path is gopkg.in/yaml.v2 ... " evaluated but not used

It is not possible to name a query parameter "type" because it is wrongly interpreted by the parser.

Here is the error:

Failed parsing RAML file test.raml:
  Error parsing RAML:
  yaml: line 204: mapping values are not allowed in this context

The raml file looks like:

/myTest:
    get:
        description: Test
        queryParameters:
            param1:
                displayName: First parameter
                type: string
                example: hello
                required: true
            type:
                displayName: My type
                type: string
                required: false   

I'm interested in RESTful API, and also Go Language.Simple & Concurency.

Can't help to image that there is a tool chains for auto build Full Stack RESTful Project, :P I'm very lazy.

I prefer to use Angularjs, Atom-shell, Ionic for Client(both pc & mobile) & Golang for Service

I don't admire Java, so will never use https://github.com/mulesoft/raml-for-jax-rs

About RESTful Front-End

There is already a generator for angularjs,
and a generator for js.
It's not perfect but enough.

About RESTful Back-End

I'm watching this project for a long time:
https://github.com/ant0ine/go-json-rest,A golang simple rest framework, with a nice "gorm", witch support "Migration", to generate database automaticly.

• need a generator for this framework
• or a good ORM embed within "go-raml"

I'm developing a raml-generator, and want to find which Parser is the best one.

Considering file handling I/O performance , Go is the best language to generate a large number of static files. Like this one, hugo http://gohugo.io/.

So, I Choose go-raml/raml. When will it support raml v1.0?

I'm looking forward to.

It shows about a year ago the last update. Does this fully support 0.8 spec? Is there work ongoing to support 1.0 now?

Hi,

In the past year, I have come to accept that I currently do not have sufficient time to dedicate to go-raml/raml development. go-raml/raml is currently the most popular golang RAML parser in Github (and hence - the world!! 😉). Mulesoft have shown interest in the project, possibly in assisting development or in sponsoring it. There's a lot of potential here.

I had a lot of fun working on it in the past and had big plans for it, including an implementation of the v1.0 spec, and the validator (which goes into validating traits, schemas and other 'by-name' references, JSON Schema and XML Schema, and more), and of course the many TODOs that litter the code. Oh, and naturally - an integration with a RESTful go library, and auto-generation of servers/clients. But then came entrepreneurial life.

This project deserves better, and as such I am looking for additional maintainers to assist or even take over.

Please comment here if:

1. You are currently interested in helping or taking over,
2. You make use of go-raml/raml or know someone who uses this project in a production setting,
3. Can suggest potential maintainers or sponsors.

I am tagging various developers who showed interest in assisting with the project, or who forked it:
@jstoiko @arbrix @postatum @burrbd @buddhamagnet @elgris @stunti @prisamuel @ryanemax @robvanmieghem @iwanbk @despiegk

Thanks and have a great day. :)

/albums:
    get:
        description: Retrieve a list of albums
    post:
            description: Create a new album
    /{isrc}:
        uriParameters: 
      isrc:
        description: The International Standard Recording Code which uniquely identifies this album
        type: string
        pattern: ^[a-zA-Z]{2}\-[0-9a-zA-Z]{3}\-\d{2}\-\d{5}$
        get:
            description: Retrieve the specified album
        put:
            description: Update an album        
        delete:
            description: Delete this album

The pattern field in the above raml example gets ignored when matching handlers to methods. When there are multiple handlers which support different types of UriParameters for the same resource, this is useful.