The api-definition-raml.yaml is the one from source control. The other file is what is generated from exporting from Restlet Studio. As you can see, the formats are widely different, so how are you using the tool, while also keeping the current format?

Shalom,
Chongsun

-- ​
There are 10 kinds of people in this world; those who understand binary, and those who don’t.

Software Development Engineer
 
VillageReach Starting at the Last Mile
2900 Eastlake Ave. E, Suite 230,  Seattle, WA 98102, USA
DIRECT: 1.206.512.1536   CELL: 1.206.910.0973   FAX: 1.206.860.6972
SKYPE: chongsun.ahn.vr
Connect on Facebook, Twitter and our Blog

On Aug 4, 2016, at 12:39 AM, Paweł Lal <plal@soldevelo.com> wrote:

Hi Chongsun,

As I see, RAML broke after change made by someone from the ToP, probably they use other way to edit it. The only manual change my team does during RAML creation is adding headers and body to response as well as indentations for code readability.

Best regards,
Paweł Lal

On Wednesday, 3 August 2016 20:59:16 UTC+2, chongsun.ahn wrote:
Hey Pawel,

The import to Restlet Studio is working now because I fixed the issues in the RAML in this commit: https://github.com/OpenLMIS/openlmis-requisition/commit/fda4c8d1855f7bf2092480c7b4f55ba940e478bb. If you check out the previous commit, and try to import the RAML into Restlet Studio, you will see the errors.

Additionally, I am not sure how the file comes to its present format, as the export from Restlet Studio gives a very different RAML format than what is in source control. Can you explain how you take what you get from Restlet Studio and turn it into what is in the source?

Shalom,
Chongsun

-- ​
There are 10 kinds of people in this world; those who understand binary, and those who don’t.

Software Development Engineer
 
VillageReach Starting at the Last Mile
2900 Eastlake Ave. E, Suite 230,  Seattle, WA 98102, USA
DIRECT: 1.206.512.1536   CELL: 1.206.910.0973   FAX: 1.206.860.6972
SKYPE: chongsun.ahn.vr
Connect on Facebook, Twitter and our Blog

On Aug 3, 2016, at 8:31 AM, Paweł Lal <pl...@soldevelo.com> wrote:

Hi Rich,

If it comes to AYIC, we mostly use Restlet Studio for writing RAML files with small handmade adjustements (indentations, typos). I checked api-definition.yaml and also api-definition-raml-yaml (generated) and they both load into Restlet Studio. 
Could you provide me the error message you got after unsuccessful load? Used RAML file would also be useful.

Kind regards,
Paweł Lal


On Tuesday, 2 August 2016 19:55:08 UTC+2, Rich Magnuson wrote:

Soldevelo teams:  how are you writing the RAML files?  Are you using a tool or rolling it by hand?  We’ve noticed the requisition RAML file doesn’t load into Restlet Studio.

 

We also wondering if we should break up the RAML file into separate files, should they become so large it is difficult to read or maintain.  Could our existing processes – to generate HTML doc, the testing, the swagger conversion – could they handle multiple RAML files?

 
 

We talked a bit about this in Seattle.  We don’t want to be tied to a tool, but want to at least write acceptable RAML, preferably with some sort of validator.  However we’re doing it now seems to be accepted by other tools (like RestAssured, swagger, etc.), so we can continue down what we’re doing for right now, but some validating assistance would be good.

 

Rich


-- 
You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev...@googlegroups.com.
To post to this group, send email to openlm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/3246246d-ce84-40e0-a2a1-4519513d3b9b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com.
To post to this group, send email to openlmis-dev@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/7f1a2932-4184-4661-9188-05752caf61a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.