Background

When building out a JSONAPI, every endpoint has a type field with a fixed value of the resources name. Writing parameter :type, 'The object type', value: 'users' is more clear of it's static nature than looking for a let.

More broadly, when using rspec_api_documentation for 10-15 projects now. Having let reserved for dynamic values and using value: 3 for things that are static, seems to reduce the "noise" in writing larger spec files.

Need Feedback

Not 100% sure on the value: naming convention. I also tried having method support a block (like method: -> { '3' }), but that did not feel right.

Notes

• The specs suite does not seem to like Ruby 2.5.0 with the current Gemfile.lock. I suggest removing the Gemfile.lock from the repo (gitignore it) and depend on the gemspec.
• I had to upgrade the json gem in order to run bundle on Ruby 2.5 / OSX 10.13