Closed blakeembrey closed 7 years ago
It seems that, since RAML is based on YAML, we should be able to easily dump the expanded version as JSON no?
There are some yaml2json npm modules that we could use.
@blakeembrey you told me yesterday that you will continue to use the TCK. Shall we still leave that here open?
I think this is still valuable and should exist. However, considering that the output of the low level may not be consistent and there's a discussion to have around the expand
feature working with the JSON structure, I'm not sure I want to put it in the critical path right now for engineering. It's unfortunate, but it's just a little too late from me right now.
OK - Let's keep that open.
This does belong somewhere else, but since we're all discussion JSON here it seems relevant. Is it possible to get a raw dump of RAML -> JSON with the most basic include/overlay support? This would be hugely useful, as the dependency to create 0.8-compatible object models can be offloading onto me to develop and we can minimise the opinionated conversations around how the object model should look. This would reduce turn-around time on the structure and allow development on functional utilities that just accept object structures (even better, we can type the structures in TypeScript and development speed will increase exponentially).