Pavel Petrochenko

In your example you use: `TemperatureSensorEvent | TemperatureSensorEvent` so it should validate against `TemperatureSensorEvent` type and it will not pass validation. If you will change ` TemperatureSensorEvent | TemperatureSensorEvent` to...

It has every HumiditySensortEvent required property and one additional property which is not defined in HumiditySensortEvent as we all agreed RAML types are open by default , but in examples...

> Also in the case of resource types and traits fragments, they cannot be fully parsed till the parameter >values are known. Why? Of course you have to create a...

> There is no way to parse it as the parameter is can not be resolved until is being invoked then there is no way to know what type of...

According to me for IDE needs it is good to have: - trait/resource type structure. - for each trait/resource type use - parameter values - also it would be nice...

Actually we have most of it in our fork https://github.com/petrochenko-pavel-a/raml-java-parser (however I am not sure how easy will be to merge it back)

Actually this is not enough, because ideally we would like to have a mapping of RAML model objects on source lines

Hi This feature depends from https://github.com/raml-org/raml-java-parser/pull/51 As soon as it will integrated we will get it automatically. Regards, Pavel

This works fine in RAML 0.8 as well as in current JS parser to, I see no clarifications in spec saying that this is dissalowed. @sichvoge , @usarid what is...

Hm. I do not see any priority specified in RAML 1.0 spec. (@sichvoge may be it should be clarified), but it was handled differently in RAML 0.8 (the sample which...