Skip to content

Conversation

@rdohms
Copy link

@rdohms rdohms commented Sep 20, 2016

In our system we are gradually documenting everything, so not every method is fully documented.
Its valid raml to have

/some-resource:
    put:
    get:

This means the method is accepted, but there is no further documentation.
The current implementation does not allow this, since the value of the put key will be null.

Is this accepted behaviour? if so i'll write some tests for it.

In out system we are gradually documenting everything, so not every method is fully documented.
Its valid raml to have
```yaml
/some-resource:
    put:
    get:
```

This means the method is accepted, but there is no further documentation.
The current implementation does not allow this, since the value of the `put` key will be `null`.
Allows the lib to match things like:
```
/v2:
  /account/avatar/{id}:
    get:
```
 by looking ahead not just for current "part" but entire left over string

Needs to be improved to search for all possible matches.
Used the wrong function, replaced with strstr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant