I think that it would be beneficial/helpful to allow - optionally - RAML specifications to be parsed with some linting rules in effect. This would help organizations standardize APIs across RAML files and between various developers and teams.
Has there been any discussions on an idea like this?
Does anyone else agree that this could be a good addition?
#%RAML 0.8 title: API with lint error /Accounts: get:
The standard an organization might want to enforce is lower casing all defined URI parts
#%RAML 0.8 title: Conforming API definition /accounts: get:
To allow RAML editors to “opt-in” to linting a linter preferences file could be added to the project; similarly to something like JSHint. This way rules could be applied for those organizations that would like to define rules while not inconveniencing anyone who would not like to use linting.