Collection and member resourceTypes in our RAML; still being used?

Hello everyone,

I have noticed that for multiple microservices, we have defined collection and member resourceTypes in our RAML file, but they do not appear to be used anywhere else in the file. Are we using these, or are these old definitions no longer in use? If they are not being used, I would like for us to eventually remove them, especially since they reference a user-defined parameter (<>) which is causing raml-cop to flag warnings during RAML validation. If someone knows their origin and use, please chime in; thanks.

Shalom,

Chongsun

– ​

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

Chongsun Ahn | chongsun.ahn@villagereach.org

Software Development Engineer

Village****Reach* ** 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

www.villagereach.org

Connect on Facebook****, Twitter** ** and our Blog

I guess it might be from here: http://raml.org/developers/raml-200-tutorial#step-introduction

···

On Tuesday, February 28, 2017 at 3:55:03 AM UTC+8, chongsun.ahn wrote:

Hello everyone,

I have noticed that for multiple microservices, we have defined collection and member resourceTypes in our RAML file, but they do not appear to be used anywhere else in the file. Are we using these, or are these old definitions no longer in use? If they are not being used, I would like for us to eventually remove them, especially since they reference a user-defined parameter (<>) which is causing raml-cop to flag warnings during RAML validation. If someone knows their origin and use, please chime in; thanks.

Shalom,

Chongsun

– ​

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

Chongsun Ahn | chongs...@villagereach.org

Software Development Engineer

Village****Reach* ** 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

www.villagereach.org

Connect on Facebook****, Twitter** ** and our Blog

Hey Pengfei,

Yes, it does seem like there was a desire to use them at some point; however they don’t appear to be used anywhere in the RAML. Additionally, the definitions don’t seem to be correct. This entry (https://github.com/OpenLMIS/openlmis-referencedata/blob/master/src/main/resources/api-definition.yaml#L391 ) says it should return a 404 when the collection is empty, which is not accurate (should return a 200 with an empty array).

Shalom,

Chongsun

– ​

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

Chongsun Ahn | chongsun.ahn@villagereach.org

Software Development Engineer

Village****Reach* ** 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

www.villagereach.org

Connect on Facebook****, Twitter** ** and our Blog

···

On Feb 27, 2017, at 6:21 PM, > pfcui@thoughtworks.com wrote:

I guess it might be from here: http://raml.org/developers/raml-200-tutorial#step-introduction

On Tuesday, February 28, 2017 at 3:55:03 AM UTC+8, chongsun.ahn wrote:

Hello everyone,

I have noticed that for multiple microservices, we have defined collection and member resourceTypes in our RAML file, but they do not appear to be used anywhere else in the file. Are we using these, or are these old definitions no longer in use? If they are not being used, I would like for us to eventually remove them, especially since they reference a user-defined parameter (<>) which is causing raml-cop to flag warnings during RAML validation. If someone knows their origin and use, please chime in; thanks.

Shalom,

Chongsun

– ​

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

Chongsun Ahn | chongs...@villagereach.org

Software Development Engineer

Village****Reach* ** 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

www.villagereach.org

Connect on Facebook****, Twitter** ** and our Blog

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/9e00b32a-1df5-4e22-a3b9-ca65003f64b5%40googlegroups.com
.

For more options, visit https://groups.google.com/d/optout.