Sha256: 43ab3f4d1cbe5d2d8057834d23e1bdab543e8e42d420621db7a19b2d3629c764
Contents?: true
Size: 1.67 KB
Versions: 4
Compression:
Stored size: 1.67 KB
Contents
Feature: nested schema scaffolding
If your API endpoint has some dynamic segment - Lurker can handle it as well!
Scenario: scaffold a json schema for a "repos/show" in a nested controller spec
Given a file named "spec/requests/repos_spec.rb" with:
"""ruby
require "spec_helper"
describe Api::V1::ReposController, :lurker do
let!(:user) do
User.where(name: 'razum2um').first_or_create!.tap do |u|
u.repos.create!(name: 'lurker')
end
end
it "shows a user's repo" do
get "api/v1/users/#{user.id}/repos/#{user.repos.first.id}"
expect(response).to be_success
end
end
"""
When I run `bin/rspec spec/requests/repos_spec.rb`
Then the example should pass
Then a file named "lurker/api/v1/users/__user_id/repos/__id-GET.json.yml" should exist
Then the file "lurker/api/v1/users/__user_id/repos/__id-GET.json.yml" should contain exactly:
"""yml
---
description: repo
prefix: repos management
requestParameters:
properties: {}
required: []
responseCodes:
- status: 200
successful: true
description: ''
responseParameters:
properties:
id:
description: ''
type: integer
example: 1
user_id:
description: ''
type: integer
example: 1
name:
description: ''
type: string
example: lurker
required: []
extensions:
method: GET
path_info: "/api/v1/users/1/repos/1"
path_params:
action: show
controller: api/v1/repos
user_id: '1'
id: '1'
suffix: ''
"""
Version data entries
4 entries across 4 versions & 1 rubygems