svacas
svacas
The table should also include any default value information, right now for some fields is included in the table and for others it is described in a separate paragraph (e.g:...
both RFCs also cover [relative URI format](https://tools.ietf.org/html/rfc3986#section-4.2). For us it allows exposing the same RAML on different endpoints without need of rewriting the baseUri attribute.
that's OK, I thought you were implying that `baseUri` must be absolute, as per the grammar snippet you pasted it.
Looks a bit counter-intuitive to treat a parameter that resolves to value `X` different than the literal value `X`. What will happen when you mix things? e.g.: `type: suffix-` I'm...
after discussing with several raml users we arrived to the following proposal: references are resolved first in the context where they were defined and if not present there they are...
I'll try to summarize your approach to check if we are on the same page: - references from explicit parameters are resolved in the context where the value is assigned,...
The problem with this approach is that a library cannot be validated in isolation. It will be only valid when referenced from RAML files which have a default media type...
!include used to mean that the whole content of the referenced file was inlined. Now it is not clear what's the final content to be included as for fragments some...
Can you describe the behavior you would like to have?
At the moment the model cannot be modified and there's no emitter yet. The idea is to implement both features in the near future.