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
When generating a Ruby client, RSpec files are created with reference comments to https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers. However, since RelishApp is currently unavailable, the referenced content cannot be accessed. The content is accessible on https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ .
ref: https://rspec.info/documentation/
OpenAPI Generator version: 6.5.0
I suggest that replace the URL https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers with a valid RSpec documentation URL, such as https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ .
The text was updated successfully, but these errors were encountered:
can you please file a PR with the suggested change? thank you.
Sorry, something went wrong.
I opened PR: #15164
Successfully merging a pull request may close this issue.
Description
When generating a Ruby client, RSpec files are created with reference comments to https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers. However, since RelishApp is currently unavailable, the referenced content cannot be accessed.
The content is accessible on https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ .
ref: https://rspec.info/documentation/
openapi-generator version
OpenAPI Generator version: 6.5.0
Suggest a fix/enhancement
I suggest that replace the URL https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers with a valid RSpec documentation URL, such as https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/ .
The text was updated successfully, but these errors were encountered: