Path aliases

[P0lip]

User story.
As a ruleset write, I often have to come up with complex JSON Path expressions in order to pick a certain fragment of my document I'd like my rule to be run on.
This is both tedious and error-prone, in particular when targeting specific specs like OpenAPI.

Describe the solution you'd like

I'd like to have a way to specify these complex path expressions in one spot to be able to re-use them later on.
Ideally, the rulesets Stoplight provides have an array of paths I could choose from, so that I don't need to author my own paths anymore (assuming I write a ruleset based on OpenAPI / AsyncAPI)

Additional context

This issue just intend to add the functionality to specify those aliases which can then be used in the ruleset and rulesets extending it.

Stoplight ruleset having aliases would be tackled in a separate issue.

[stoplight-bot]

🎉 This issue has been resolved in version @stoplight/spectral-core-v1.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀