Skip to content
This repository has been archived by the owner on Dec 20, 2021. It is now read-only.

doc: add clarity to spec definition in README #21

Merged
merged 1 commit into from
Apr 19, 2019

Conversation

MeroveeCharrue
Copy link
Contributor

This is a note in the doc to prevent potential known issues when declaring endpoints to match routes.

@coveralls
Copy link

coveralls commented Apr 17, 2019

Coverage Status

Coverage decreased (-0.4%) to 93.194% when pulling 83490c8 on MeroveeCharrue:apispec-description-order into c3a0823 on RETFU:master.

README.md Outdated
> Note: Currently, the order of API definitions matters. See this as an example :
> ```raml
> /item/{itemId}
> /item/archive
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add a working example, specify that this is a best practice and warn about the side effect if not applied.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I've rephrased it to emphasis good practice.

@RETFU
Copy link
Owner

RETFU commented Apr 19, 2019

@yannickroger good for you too?

@yannickroger
Copy link
Collaborator

@RETFU 👍

@RETFU RETFU merged commit 6138ec5 into RETFU:master Apr 19, 2019
@MeroveeCharrue MeroveeCharrue deleted the apispec-description-order branch January 26, 2021 18:56
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants