Allow setting current resource in tests

[00dav00]

Allows setting current_resource on specs using with graphql schema test shared context

Closes #138

[mcelicalderon]

Why not the shorter version?

context[:current_resource] ||= resource_names.find do |resource_name|

[mcelicalderon]

Looks good, just a small suggestion and don't forget to remove commented code.

[keithmgould]

This is super cool -- I see that its closed now but is there a way for new users of the gem to know about how to properly test? Maybe a readme section could be added show the methods included in this PR, or at least a link from readme to the above?

[00dav00]

Hi @keithmgould , I think that is a great suggestion!
Would you like to create a PR with that addition to the README?

[mcelicalderon]

I can also do that if no one has done it until I get some time. Important thing to note here is that this is a quick fix that works for all but one scenario, passing no current_resource for an authenticated query. This will still throw an error unless you stub the controller injected in the context. A more complete fix is still on the works as it might require a bigger refactor of how we set the current user in the context and also the removal of queries and mutations that return http redirects in favor of simpler confirmation and password reset flows. This way we might be able not to require the controller to be injected all together