Closed fishermand46 closed 9 years ago
It makes sense, except that I would like to get away from RequestClause having attributes at all, so that it just an interface that should be implemented by subclasses for specific contract formats (Swagger, RAML, whatever).
I guess I need to find time to make RequestClause abstract and create a subclass for LegacyRequestClause.
That sounds like a good direction to move. :thumbsup:
I'm getting
lib/pacto/stubs/webmock_adapter.rb:95:in
block in strict_details': undefined methodempty?' for nil:NilClass (NoMethodError)
when I try to stub_providers with pacto. I tracked it down to the request_clause.headers being nil.Test code:
Here you can see that headers in request_clause has no default value. But in the response clause, headers defaults to
{}
. I think it should in request_clause as well.