-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't pass request environment to renderer when calling sync actions #214
Comments
This would definitely be a breaking change. I would suggest building out a small DSL for things to be passed to the sync render context, possibly by leveraging a library like That way, the breaking changes would be minimized and would still guarantee quite a bit of flex. |
Just following up. Was anyone able to resolve this issue? I am still getting the
when using current_user in the views. |
Was anyone able to resolve this issue? Ran with pusher and faye and I am still receiving the following error:
The message object is being created, so when page refreshes the new message is there. Here is a look at the controller:
calling the partials:
partial:
|
Problem
current_user
,params
, etcsync_update
(orsync_new
) are called from inside of a request environment, they can access the variables inside of that environmentcurrent_user
is called withoutrefetch: true
#190 might be an example of one of these)Solution
The text was updated successfully, but these errors were encountered: