You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 17, 2024. It is now read-only.
RAML 1.0 has been released almost 5 years ago, in May 2016. Over time, a number of typos, grammatical errors and inconsistencies have been spotted and reported by the RAML community. We finally got around to fix most if not all those issues and are bundling all those clarifications in a single 1.0.1 patch release.
Does this affect my existing RAML 1.0 definitions?
No, this 1.0.1 release is a patch which means that it does not affect the validity of existing RAML 1.0 API definitions. In other words, the #%RAML 1.0 header remains unchanged.
What's included in this patch release?
The v1.0.1 Milestone contains all the clarifications that will be included in this release. Most small typos have been grouped together and are listed here. These clarifications have also been ported to the RAML TCK, our official test suite for RAML processors.
When will it be released?
We don't have an official date because we want to first gather feedback, and then fix a date later on based on that feedback. This page will be updated as soon as a release date has been
Where do I provide feedback?
Feel free to provide feedback in any of the individual issues. If your comment or feedback is of general nature, feel free to leave it on this issue directly. You can also discuss this on the official RAML community Slack "raml-api" workspace which you can join here if you're not already member.
The text was updated successfully, but these errors were encountered:
What is this about?
RAML 1.0 has been released almost 5 years ago, in May 2016. Over time, a number of typos, grammatical errors and inconsistencies have been spotted and reported by the RAML community. We finally got around to fix most if not all those issues and are bundling all those clarifications in a single 1.0.1 patch release.
Does this affect my existing RAML 1.0 definitions?
No, this 1.0.1 release is a patch which means that it does not affect the validity of existing RAML 1.0 API definitions. In other words, the
#%RAML 1.0
header remains unchanged.What's included in this patch release?
The v1.0.1 Milestone contains all the clarifications that will be included in this release. Most small typos have been grouped together and are listed here. These clarifications have also been ported to the RAML TCK, our official test suite for RAML processors.
When will it be released?
We don't have an official date because we want to first gather feedback, and then fix a date later on based on that feedback. This page will be updated as soon as a release date has been
Where do I provide feedback?
Feel free to provide feedback in any of the individual issues. If your comment or feedback is of general nature, feel free to leave it on this issue directly. You can also discuss this on the official RAML community Slack "raml-api" workspace which you can join here if you're not already member.
The text was updated successfully, but these errors were encountered: