I use the spectral linting plugin for linting against the OpenApi3 spec with your plugin, which is very convenient and good to use.
Normally I configure a path to the spec which is the ruleset for my own *.yaml file. This works well. At the moment my file has no errors but some warnings. These are the same result as in normal pipelines with our spectral-tests.
When I remove the path from the settings and throw in the same spec as ".spectral.yaml" into the workingdirectory (same directory as my *.yaml is located) the warnings turn into errors.
This behaviour seems to be somehow a bug. So it seems the local file is interpreted but in a total different way. Sorry, I cannot provide you the files as they are internal. When I remove the ".spectral.yaml" again and set the property to the same file on another location it's working again. Shown correctly as "warning"
I use the spectral linting plugin for linting against the OpenApi3 spec with your plugin, which is very convenient and good to use.
Normally I configure a path to the spec which is the ruleset for my own *.yaml file. This works well. At the moment my file has no errors but some warnings. These are the same result as in normal pipelines with our spectral-tests.
When I remove the path from the settings and throw in the same spec as ".spectral.yaml" into the workingdirectory (same directory as my *.yaml is located) the warnings turn into errors.
This behaviour seems to be somehow a bug. So it seems the local file is interpreted but in a total different way. Sorry, I cannot provide you the files as they are internal. When I remove the ".spectral.yaml" again and set the property to the same file on another location it's working again. Shown correctly as "warning"