Skip to content
This repository has been archived by the owner on Feb 17, 2024. It is now read-only.

Patch Release 2016/29/07

Compare
Choose a tag to compare
@sichvoge sichvoge released this 29 Jul 11:44
· 105 commits to master since this release

To our lovely RAML Community,

The RAML Workgroup is happy to ship a set of patches to our specification today. We don't bump any major or minor version for that, so everything stays as it is. The current version still be RAML 1.0! This patch release contains the usual clarification, content, and other fixes that will improve the specification.

What changed?

Most changes are around clarification such as the any type or what kind of other built-in types do we have. People felt that this was missing, and we listen to all of you! You will find two brand new section here (the "Any" type) and here (Built-in Types). Furthermore, we changed the null type to nil to align better with the YAML spec. This change might impact existing RAML documents, but we did not want to wait until a minor release. Therefore, we think the best time for this is as early as possible.

Every other change was more around content improvement or fixing issues on examples. You can view a full list of changes here.

Will there be other patch releases coming?

There will be most likely. Patch releases help us to improve the overall quality of the specification. Although we will not do any significant changes that impact existing RAML 1.0 specification; that we save for any future versions (major or minor) of the RAML specification.

The current pipeline for the next patch release are: clarifications on the union type to clarify what type: union is, and an algorithm how to resolve traits and resource types parameter. The former not introducing any changes to the current way using type expressions. No worries :)

Please continue to raise issues, give us advises and feedback, so that we can continue to improve RAML together.

The RAML Workgroup