Mariano de Achaval
Mariano de Achaval
It will really help us to start building tooling around a language be are creating.
You should use libraries this is the best way to reuse any element as later you can reference it. On Tue, Aug 23, 2016 at 1:20 PM, deem0n [email protected] wrote:...
@ddenisenko And what about the other Santiago's scenario `type: suffix-`. Is this suppose to be resolved in the param context or in the library.
This I don't get it because we can get more creative and `hA2` key be a parameter. ` : Monkey` Is this still resolved to libA.raml? Also what happen if...
In my opinion having libraries being resolved relative to the root raml makes them not portable. This means that if they are open by any editor it is going to...
> You cannot just restrict them to root and libraries as that would also restrict use cases like extending data types from one that has been defined in a library,...
So my question is why do we think is better to only allow **uses:** in typed fragments. My vote is first remove it from both and force people to use...
> Because you're declaring that a document is indeed a RAML document of a particular type, so it makes sense to put in constructs like libraries. Otherwise it's not a...