rspec-openapi
rspec-openapi copied to clipboard
exoego
Generate OpenAPI schema from RSpec request specs
Hi, I have some rspec test with data: ```ruby let(:data) { { description: {}, type: "closed", max_rating: 1, answer_options: [ {id: first_answer_option.id, description: "description", correct: false}, {id: second_answer_option.id, description: "NOT...
This morning, We encountered a strange issue when integrating this gem with our Minitest test suite. Sometimes, the OpenAPI schema was generated, sometimes not. In the end, we discovered that...
Hey :) Using this gem we noticed that having predictable data in different run can be useful if you are going to regenerate the OpenAPI documentation (fully or partially). To...
When running `OPENAPI=1 rspec spec/requests/samples_spec.rb:15` is run, the schema that is not under test is also deleted. request spec ```ruby describe 'Sample API TEST', :api_admin, type: :request do let(:headers) {...
In some situations, I was my test to be more descriptive, but I don't necessarily want my docs to have the same description. However, when I customize the description on...
issue: https://stackoverflow.com/questions/68452127/pass-array-as-query-parameter-in-swagger-openapi-3-0
I tried to do the generation of a few examples as [described here](https://github.com/exoego/rspec-openapi/issues/177). I would like to get a review of my approach before I continue working on this feature....
Because of my specs, the following definition is generated: ``` properties: first_name: nullable: true ``` To solve that, I manually edited the generated file (as indicated [here](https://github.com/exoego/rspec-openapi?tab=readme-ov-file#how-can-i-add-information-which-cant-be-generated-from-rspec)) to have ```...
Hello good people, I hope all is well. This PR introduces three minor changes to the `rspec-openapi` gem: 1. **Header params can now be optional and by default required:** In...
