You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This resulted in some different behavior in console/development than what I could expect in the actual app. For example in the console:
def setup_new_reader
(ReadMark.readable_classes || []).each do |klass|
klass.mark_as_read! :all, for: self
end
end
would not initially do anything, until after the .have_read? call.
Should ReadMark.readable_classe be you need to setup in a config or something?
I think this may be related to eager loading in development. If Article is not loaded before a User is created (which can happen all the time in development), then this unintentional behavior will happen.
The text was updated successfully, but these errors were encountered:
I'm noticing in development ReadMark.readable_classes is nil. It's not till I made a related call that it got defined with User as a readable type.
This resulted in some different behavior in console/development than what I could expect in the actual app. For example in the console:
would not initially do anything, until after the .have_read? call.
Should ReadMark.readable_classe be you need to setup in a config or something?
I think this may be related to eager loading in development. If Article is not loaded before a User is created (which can happen all the time in development), then this unintentional behavior will happen.
The text was updated successfully, but these errors were encountered: