Import a Swagger or Open API file and create a Ruby Request Hash file including all requests and responses with all the examples. The file can be in JSON or YAML.
The Request Hash will include also the pattern (regular expressions) of the fields, parameters, default values...
The output of this gem will be following the specification of Request Hashes: https://github.com/MarioRuiz/Request-Hash
The Request Hashes generated will be able to be used with any Ruby Http Client and it is adapted even better with nice_http gem: https://github.com/MarioRuiz/nice_http
A beautiful way to access and use the generated files is by using pry: https://github.com/pry/pry
To be able to generate random requests take a look at the documentation for nice_hash gem: https://github.com/MarioRuiz/nice_hash
This is an example of a generated request hash:
# operationId: addPet, method: post
# summary: Example
# description: Creates a new pet in the store. Duplicates are allowed
# required data: name
def self.add_pet()
{
path: "/api/pets",
data_required: [
:name,
],
data_examples: [
{
name: "",
tag: "",
},
],
responses: {
'200': {message: "pet response"},
'default': {message: "unexpected error"},
},
}
end
If you want to automatically generate RSpec tests for every end point of your Swagger file, use the create_tests gem: https://github.com/MarioRuiz/create_tests
require 'create_tests'
CreateTests.from "./requests/uber.yaml.rb"This is the output of the previous run:
- Logs: ./requests/uber.yaml.rb_create_tests.log
** Pay attention, if any of the test files exist or the help file exist only will be added the tests, methods that are missing.
- Settings: ./settings/general.rb
- Test created: ./spec/User/profile_user_spec.rb
- Test created: ./spec/User/activity_user_spec.rb
- Test created: ./spec/Products/list_products_spec.rb
- Test created: ./spec/Estimates/price_estimates_spec.rb
- Test created: ./spec/Estimates/time_estimates_spec.rb
- Helper: ./spec/helper.rb
Install it yourself as:
$ gem install open_api_import
Take in consideration open_api_import gem is using the 'rufo' gem that executes in command line the rufo command. In case you experience any trouble with it, visit: https://github.com/ruby-formatter/rufo
After installation you can run using command line executable or importing from Ruby.
You have all the json and yaml examples that the Open API project supplies on /spec/fixtures/ folder. To test it you can use any of those ones or your own Swagger or Open API file.
For help and see the options, run in command line / bash: open_api_import -h
Example:
open_api_import ./spec/fixtures/v2.0/yaml/uber.yaml -fpThis is the output of open_api_import -h:
Usage: open_api_import [open_api_file] [options]
Import a Swagger or Open API file and create a Ruby Request Hash file including all requests and responses.
More info: https://github.com/MarioRuiz/open_api_import
In case no options supplied:
* It will be used the value of operation_id on snake_case for the name of the methods
* It will be used the first folder of the path to create the module name
-n, --no_responses if you don't want to add the examples of responses in the resultant file.
-m, --mock Add the first response on the request as mock_response
-p, --path_method it will be used the path and http method to create the method names
-o, --operationId_method It will be used the operationId field like it is to create the method names
-f, --create_files It will create a file per module
-T, --tags_module It will be used the tags key to create the module name
-F, --fixed_module all the requests will be under the module Requests
-s, --silent It will display only errors
-c, --create_constants For required arguments, it will create keyword arguments assigning by default a constant.
Write your ruby code on a file and in command line/bash: ruby my_file.rb
To convert the Swagger or Open API file into a Request Hash:
require 'open_api_import'
OpenApiImport.from "./spec/fixtures/v2.0/yaml/uber.yaml"
OpenApiImport.from "my_file.json"The supported HTTP methods are: GET, POST, PUT, DELETE and PATCH
The requests will be organized by modules generated from the content in the Swagger file.
For example this would be generated when run this: OpenApiImport.from "./spec/fixtures/v2.0/yaml/petstore-simple.yaml"
##################################################
# Swagger Petstore
# version: 1.0.0
# description:
# A sample API that uses a petstore as an example to demonstrate features in the swagger-2.0 specification
##################################################
module Swagger
module SwaggerPetstore
module V1_0_0
module Pets
# operationId: findPetById, method: get
# summary:
# description:
# Returns a user based on a single ID, if the user does not have access to the pet
# parameters description:
# id: (integer) ID of pet to fetch
def self.find_pet_by_id(id)
{
path: "/api/pets/#{id}",
method: :get,
responses: {
...
...The parameters can be supplied alone or with other parameters. In case a parameter is not supplied then it will be used the default value.
How the name of the methods will be generated.
Accepts three different options: :path, :operation_id and :operationId. By default :operation_id.
path: it will be used the path and http method, for example for a GET on path: /users/list, the method name will be get_users_list
operation_id: it will be used the operationId field but using the snake_case version, for example for listUsers: list_users
operationId: it will be used the operationId field like it is, for example: listUsers
require 'open_api_import'
OpenApiImport.from "./spec/fixtures/v2.0/yaml/petstore-simple.yaml", create_method_name: :pathThe output will generate methods like this:
# operationId: findPets, method: get
# summary:
# description:
# Returns all pets from the system that the user has access to
# parameters description:
# tags: (array) tags to filter by
# limit: (integer) maximum number of results to return
def self.get_pets(tags: "", limit: "")
{
path: "/api/pets?tags=#{tags}&limit=#{limit}&",
...
...if create_method_name is :operation_id
require 'open_api_import'
OpenApiImport.from "./spec/fixtures/v2.0/yaml/petstore-simple.yaml", create_method_name: :operation_idThe output will generate methods like this:
# operationId: findPets, method: get
# summary:
# description:
# Returns all pets from the system that the user has access to
# parameters description:
# tags: (array) tags to filter by
# limit: (integer) maximum number of results to return
def self.find_pets(tags: "", limit: "")
{
path: "/api/pets?tags=#{tags}&limit=#{limit}&",
...
...if create_method_name is :operationId
require 'open_api_import'
OpenApiImport.from "./spec/fixtures/v2.0/yaml/petstore-simple.yaml", create_method_name: :operationIdThe output will generate methods like this:
# operationId: findPets, method: get
# summary:
# description:
# Returns all pets from the system that the user has access to
# parameters description:
# tags: (array) tags to filter by
# limit: (integer) maximum number of results to return
def self.findPets(tags: "", limit: "")
{
path: "/api/pets?tags=#{tags}&limit=#{limit}&",
...
...How the module names will be created.
Accepts five different options: :path, :path_file, :tags, :tags_file and :fixed. By default :path.
path: It will be used the first folder of the path to create the module name, for example the path /users/list will be in the module Users and all the requests from all modules in the same file.
path_file: It will be used the first folder of the path to create the module name, for example the path /users/list will be in the module Users and each module will be in a new requests file.
tags: It will be used the tags key to create the module name, for example the tags: [users, list] will create the module UsersList and all the requests from all modules in the same file. In case the tags are equal to the beginning of the operationId then it will be removed from the method name.
tags_file: It will be used the tags key to create the module name, for example the tags: [users, list] will create the module UsersList and and each module will be in a new requests file. In case the tags are equal to the beginning of the operationId then it will be removed from the method name.
fixed: all the requests will be under the module Requests
require 'open_api_import'
OpenApiImport.from "./spec/fixtures/v2.0/yaml/petstore-simple.yaml", name_for_module: :fixedIt will generate just one file including all requests under the Requests module
module Swagger
module SwaggerPetstore
module V1_0_0
module Requests
# operationId: findPets, method: get
# summary:
# description:
# Returns all pets from the system that the user has access to
# parameters description:
# tags: (array) tags to filter by
# limit: (integer) maximum number of results to return
def self.find_pets(tags: "", limit: "")
...
...In case using :path
require 'open_api_import'
OpenApiImport.from "./spec/fixtures/v2.0/yaml/petstore-simple.yaml", name_for_module: :pathIt will generate just one file including every request under the module generated from the first folder of the path
module Swagger
module SwaggerPetstore
module V1_0_0
module Pets
# operationId: findPetById, method: get
# summary:
# description:
# Returns a user based on a single ID, if the user does not have access to the pet
# parameters description:
# id: (integer) ID of pet to fetch
def self.find_pet_by_id(id)
...
...In case using :path_file
require 'open_api_import'
OpenApiImport.from "./spec/fixtures/v2.0/yaml/petstore-simple.yaml", name_for_module: :path_fileIt will generate one file per module including every request under the module generated from the first folder of the path. Also it will be generated one file that will have all the require_relative for the generated request files.
This is the output of the run:
** Generated files that contain the code of the requests after importing the Swagger file:
- /petstore-simple.yaml_Root.rb
- /petstore-simple.yaml_Pets.rb
** File that contains all the requires for all Request files:
- /petstore-simple.yaml.rb
In case using :tags
require 'open_api_import'
OpenApiImport.from "./spec/fixtures/v2.0/yaml/uber.yaml", name_for_module: :tags, create_method_name: :pathIt will generate just one file including every request under the module generated from the first folder of the path
module Swagger
module UberApi
module V1_0_0
module Products
# operationId: unknown, method: get
# summary: Product Types
# description:
# The Products endpoint returns information about the Uber products offered at a given location.
# The response includes the display name and other details about each product, and lists the products in the proper display order.
# parameters description:
# latitude: (number) (required) Latitude component of location.
# longitude: (number) (required) Longitude component of location.
def self.get_products(latitude, longitude)
...
...If you want to add the examples of responses in the resultant file.
Accepts true or false, by default is true.
require 'open_api_import'
OpenApiImport.from "./spec/fixtures/v2.0/yaml/petstore-simple.yaml", include_responses: falseA method that will be included in the output:
# operationId: findPetById, method: get
# summary:
# description:
# Returns a user based on a single ID, if the user does not have access to the pet
# parameters description:
# id: (integer) ID of pet to fetch
def self.find_pet_by_id(id)
{
path: "/api/pets/#{id}",
method: :get,
}
endIn case we run this
require 'open_api_import'
OpenApiImport.from "./spec/fixtures/v2.0/yaml/petstore-simple.yaml", include_responses: trueA method that will be included in the output:
# operationId: findPetById, method: get
# summary:
# description:
# Returns a user based on a single ID, if the user does not have access to the pet
# parameters description:
# id: (integer) ID of pet to fetch
def self.find_pet_by_id(id)
{
path: "/api/pets/#{id}",
method: :get,
responses: {
'200': {
message: "pet response",
data: {
name: "string",
tag: "string",
id: 0,
},
},
'default': {
message: "unexpected error",
data: {
code: 0,
message: "string",
},
},
},
}
endAdd the first response on the request as mock_response to be used.
Admits true or false. By default false.
In case using nice_http gem: if NiceHttp.use_mocks = true will use it instead of getting the real response from the WS.
require 'open_api_import'
OpenApiImport.from "./spec/fixtures/v2.0/yaml/petstore.yaml", mock_response: trueIt will include this on the output file:
# operationId: listPets, method: get
# summary: List all pets
# description:
# parameters description:
# limit: (integer) How many items to return at one time (max 100)
def self.list_pets(limit: "")
{
path: "/v1/pets?limit=#{limit}&",
method: :get,
mock_response: {
code: "200",
message: "A paged array of pets",
data: [
{
id: 0,
name: "string",
tag: "string",
},
],
},
...
...The methods will be generated using keyword arguments and for required arguments, it will create keyword arguments assigning by default a constant.
def self.get_products(latitude: LATITUDE, longitude: LONGITUDE)Bug reports and pull requests are welcome on GitHub at https://github.com/marioruiz/open_api_import.
The gem is available as open source under the terms of the MIT License.