jmons/ramlwrap

Where an API is both a GET and a POST there is an issue

Closed this issue · 2 comments

jmons commented

As part of porting tests to 'better' laid out RAML, I found this test case, but it doesn't work i.e. we have no users using this feature yet.

It seems that (in the use case:

    displayName: The Get Request (requires auth)
    get:
        description: Get a feature
        responses:
            200:
                description: A response
                body:
                    application/json:
                        example: '{ "status": "ok", "logged_in_user":"no_user"}'
    post:
        description: Post a feature
        responses:
            200:
                description: A response
                body:
                    application/json:
                        example: '{ "status": "ok", "logged_in_user":"no_user"}'        

in this instance, both GET and POST seem to be a ValidatedPOSTAPI rather then the right types (?)

I'm currently working on a solution for this.

jmons commented

Fixed in @Jamian PR of #35