Support RAML v1.0 #54
Comments
|
There are 7 changes listed here - would it make sense to create new issues for each one? |
|
@pmackay yes, but I'm actually in the middle of making a roadmap to put on the (currently empty) wiki, of which more detailed issues will come from, if that makes sense. |
|
Currently scoping this out in the wiki! |
|
@econchick ooc is this still a priority? I saw the wiki link above was empty. |
|
hey @j-funk ! It's still a priority, but development has stalled because I moved to NYC a couple of weeks ago for a new job (same company). So I've been distracted with getting settled in. I guess this is part of the problem, when there's only one main developer :-! But I'm spending some time this weekend to get back up to speed. |
|
@econchick Has any work started on RAML 1.0? I'm working with another developer on laying the foundations for all of our internal API's going forward, and I think it would make more sense to add RAML 1.0 support to ramlfications than to write our own separate library. Just want to make sure I start in the right place if any work has begun. |
|
i also need this and will be looking to implement it myself, if necessary, so please anyone share what you have. initially i need to be able to load raml and create documentation from it. |
|
@jamespharaoh take a look at the other library I've released, griffin. It creates HTML/static docs from RAML files. |
|
@mcm the v0.2.0-dev branch is the current progress of RAML1.0 support. It's started, but it's slow. I'd hate for you to write something separately. I'd love for any help, which is outlined on the wiki Feel free to hop into the #ramlfications slack channel at slackin.spotify.com, or on IRC, if you want to chat. |
|
@econchick you might want to update the earlier link to the empty wiki at the top of this thread as well :) |
|
@j-funk thanks! I just did |
|
@econchick is there any specific timeline you can share for the RAML 1.0 support? |
|
Hey @sichvoge - I wish I could; it's pretty much down to just [unpaid] work on the weekends for me so it's pretty slow, and there have not been any recent contributions from others to help. I understand there's a lot of interest to get support for 1.0. Perhaps I should run a kickstarter or something to help give motivation and negate the issue of work going unpaid (sorta kidding 😉 ). |
|
HAHA :D Let me know if you need more advertisement. I am planning to add an article to the "Sneak Peek" section in the RAML forums and consolidate infos about the current tools that are in dev. Maybe there is a good chance to ask for help ;) |
|
Not sure if you are aware but you can try out the following World Music Example to test what works and what isn't working yet. The example contains 90% of all features excluding overlays and extensions. |
|
@sichvoge this is amazing, thank you! I'd love any other full examples like this, if you come across them/publish. |
|
you see all i have in the same repo ;) |
|
Any update on this? |
|
Looks like this repo is being abandonned. |
|
@EpocDotFr it has not - I've been slowly working on 1.0 support in the dev branch, with a sprint held at PyCon this year. There's been a lot of conference travel, but late July & August, development should pick back up. |
|
@econchick My bad. I didn't check the dev branch. |
|
Th development seems to be stalled for 2 years now. @econchick do you know of any alternative to work with RAML 1.0 in Python? Cheers! |
|
Hi @econchick Could you please give us an update about the RAML 1.0 support? BTW, have you seen this repo https://github.com/raml-org/webapi-parser? Maybe it could help you to speed up your development. Regards! |
|
hey @eduardo-rubio et al - I am not able to give this project the attention it deserves. I've opened up a new issue soliciting for maintainers: #162 |
Since RAML v1.0 is coming with the goal of at the end of October, this issue will be a collection of all changes (that may or may not need to be addressed in
ramlfications) - to be updated in the comments.No guarantee that
ramlficationswill be updated by when the new spec comes out, just FYI :) This is more for folks coming here wondering if this is being worked on or not.The text was updated successfully, but these errors were encountered: