lint errors by custom ruleset are reported with wrong Reference

[toschder]

When using custom ruleset, the lint errors are always reported with wrong links to "More information":

�[31mSpecification contains lint errors: 7�[0m

�[33m#/info �[36m R: API_REPO_VERS_SEMANTIC �[37m D: MUST: Use Semantic Versioning (info.version)
�[0mMUST: Use Semantic Versioning (info.version)

More information: https://speccy.io/rules/1-rulesets#API_REPO_VERS_SEMANTIC

Detailed description

This is my rule:
{ "name": "API_REPO_VERS_SEMANTIC", "object": "info", "enabled": true, "description": "MUST: Use Semantic Versioning (info.version)", "pattern": { "property": "version", "value": "^[0-9]+[.][0-9]+([.][0-9]+)?$" } },
And it was invoked with
speccy lint /path/to/swagger2openapi.file -v --rules speccy/mycompany-rules.json

I would propose to name the ruleset like given with the --rules option. Another way could be to be able to define a URL in the custom-rules.json File(s) being given.

Context

I think everyone could benefit from that. The first thing you usually will do when hitting a validation error is to look into the rule(s) - and the available description,examples and so on.

Your environment

Ubuntu, speccy 0.8.x (latest)

[philsturgeon]

The custom ruleset files will need to allow for an optional URL, and if no URL exists it should not offer the link.

Who would like to take this one on? I'm assigned on a bunch of other stuff for now, so I really need help from the community to solve issues like this.

[MikeRalphson]

oas-kit will have this functionality in the next release. In addition to the above suggested implementation, rules.url may be overridden at the individual rule level. It is expected that the user of the linter will gather a unique set of rule.url+rule.name violations to output.

[MikeRalphson]

@toschder please may I add your rule to the oas-kit wiki?

[pderaaij]

This will be solved by #266

[djtarazona]

This has been fixed in v0.10.0