We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The custom example groups in RSwag (for example response) do not support symbol-style example metadata.
response
Example spec:
response "201", "article created", :skip_bullet do # ... end
This is perfectly valid in RSpec, but leads to the following error inside RSwag:
NoMethodError: undefined method `[]=' for :skip_bullet:Symbol
The spec should be equivalent to the following, which works just fine:
response "201", "article created", skip_bullet: true do # ... end
This became a problem with the new MetadataStyle cop in rubocop-rspec, which has support for two enforced styles, hash or symbol.
MetadataStyle
hash
symbol
Rubocop understands that response defines an example group with the following config:
RSpec: Language: ExampleGroups: Regular: - response
The version of are you using for:
Not related to OAS
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
The custom example groups in RSwag (for example
response
) do not support symbol-style example metadata.Steps to Test or Reproduce
Example spec:
This is perfectly valid in RSpec, but leads to the following error inside RSwag:
Expected behavior
The spec should be equivalent to the following, which works just fine:
Additional context
This became a problem with the new
MetadataStyle
cop in rubocop-rspec, which has support for two enforced styles,hash
orsymbol
.Rubocop understands that
response
defines an example group with the following config:Dependency versions
The version of are you using for:
Relates to which version of OAS (OpenAPI Specification)
Not related to OAS
The text was updated successfully, but these errors were encountered: