Simplify RAML Using Resource Types and Traits

If you read my RAML Tutorial article, then you may have wondered whether the API definitions always have to be verbose, or if there are some shortcuts one can take in order to capture common patterns found in an API in order to simplify its definition.

If so, then you may enjoy Eliminate Redundancies in RAML Using Resource Types and Traits, the second article in the RAML series that I am currently writing for the Baeldung site.

The next article in the series will focus on modularization in RAML via the use of includes, libraries, overlays, and extensions.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s