Rspec cannot detect a owner from current_user. about public_activity HOT 8 CLOSED

When you use procs to resolve such values, we expect you to store controller for our use. In model tests, you probably don't want to create controllers, so it would be convenient for you to mock this functionality and trust that it works on our side.

from public_activity.

Thank you

from public_activity.

And if I'm not mistaken, if you use Proc.new{ |_, model| model.dependent_logic } it should work too, but you won't be able to refer to the controller, obviously. The _ works like in Go language, you use it when you acknowledge the variable, but do not need it.

from public_activity.

In functional tests, you can set the controller like this:

PublicActivity.set_controller(@controller)

from public_activity.

I remove current_user out of a model. If you put current_user in a model, you cannot create a new object in the Rails console.

from public_activity.

Interesting, we do want to allow that, can you check how it works when you explicitly pass owner object? It should not exec procs then, but if it does, I'll fix it.

from public_activity.

So whats the current best practice for solving this issue when using the rails console? Do you need to PublicActivity.set_controller? It would be neat if we didn't need to access a controller at all from the model, in either case...

from public_activity.

set all params that you are usually resolving with procs before creating the activity

from public_activity.