Denis Tataurov

hey @pirj have you worked on this one? I like the idea and I'm curious if I can sneak the implementation :)

Yes, good to add negated matcher as well. It will be quite handy and readable to see something like: ```ruby expect { subject } .to have_enqueued_sidekiq_job(FooJob) .and have_enqueued_sidekiq_job(BarJob) .and avoid_enqueuing_sidekiq_job(BazJob)...

In my case it works fine in any env but test: it fails with the following message in the test example: ``` ** (EXIT from #PID) exited in: GenServer.call(#PID, {:phoenix,...

I've recently upgraded from patched 0.9.5 version to 0.10.2. I want to share with my adapters and common changes in codebase: https://gist.github.com/sineed/9c9a5d837d558e79309f90919a9b7aad. For example, for `root: false` option I've implemented...

I think my solution is quite specific that is why I created gist. I don't think that it is a good idea to make it like general solution for everyone....

I want to add that now it is not easy to declare information about relationship. For example, to create a Comment I need to specify its Post and User: ```...

@oestrich yes, I think I can find some time to implement this

I found [here](https://github.com/zipmark/rspec_api_documentation/blob/master/lib/rspec_api_documentation/dsl/endpoint.rb#L153) that I can use the following declaration to accomplish my case: ``` ruby let(:data_relationships_user_data_id) { user.id } let(:data_relationships_post_data_id) { post.id } ``` Looks quite heavy but I...

@oestrich I can make a PR anyway if you wish

No, it fits my needs. If I'll need to extend some functionality I'll ping you. For now I just use my branch.