Provide safe defaults when loading a collection that has no version number

[nmasse-itix]

Provide safe defaults when loading a collection that has no version number

[forceedge01]

Where exactly does one specify a version? I've just created a postman collection to test microcks out - I am getting the error but not much what to do about it (on the web and your resources).

EDIT: I stand corrected, found it here https://microcks.io/documentation/using/postman/#conventions

[prouwens]

Well I find having a version is good anyway, but yes I agree having a message telling so would be good and we should catch the exception as it s causing a null pointer exception.

[lbroudoux]

Safe default is not really "safe"' as it opens the door for collisions when importing service definition. I thing going with a clear and explicit error message regarding Missing version property in the collection is the right way to go.

[nmasse-itix]

With the error message, would it be possible to have a short help message explaining the required syntax "version=x.y - something" and where to set it (in the postman collection properties, field "description") ?

[lbroudoux]

@nmasse-itix I think having this kind of message, displayed on the line corresponding to Job for service:

What do you think?

[jcordes73]

According to https://schema.getpostman.com/json/collection/v2.1.0/docs/index.html, Postman supports a version field starting from Collections 2.1 (maybe). Could we use this one, instead?

[lbroudoux]

That's a really good point and a definitive enhancement for Postman Collection! For now, we only support 2.0 Collection format but it deserves an enhancement to support 2.1.

[lbroudoux]

Have created the issue #54 to track this enhancement.