"Parameters should have a description" rule in schema ruleset is (too?) broad

[shockey]

Inputs

openapi.yaml

openapi: "3.0.0"

components:
  parameters:
    MyParam:
      type: object
      properties:
        content: # Warning: Parameters must have a description.
          type: string
  schemas:
    ObjectSchema:
      type: object
      properties:
        content: # Warning: Parameters must have a description.
          type: string
    SchemaWithAPropertyNamedProperties:
      type: object
      properties:
        type: string # Warning: Parameters must have a description.

.spectral.yaml

extends:
- https://raw.githubusercontent.com/openapi-community/style-guide/master/schema-ruleset.yaml
rules: {}

Output

/Users/kyle/Documents/Stoplight Studio/gh/swagger-api/swagger-petstore/reference/test.yaml
  8:17  warning  parameter-description  Parameters must have a description.
 14:17  warning  parameter-description  Parameters must have a description.
 19:20  warning  parameter-description  Parameters must have a description.

---

I'm not certain this is a bug, but there are a couple of oddities here IMO:

• this error is being generated outside of Parameter Objects, but the error hints at Parameters specifically
• this error is being applied to freely-named key positions (e.g. in SchemaWithAPropertyNamedProperties)

I might just be missing something. Let's discuss!

[philsturgeon]

It should probably only be for stuff inside 'parameters' ey.

[philsturgeon]

Can you fire a PR that solves this @shockey? I've got a few too many plates in their air.