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
Some users would like to turn comments and/or reactions on or off on a per-status or per-post level. Potentially allow that to be set on each individual resource. Investigate how to do that.
One possibility is to add those settings to each individual resource.
One possibility is to use a join table to tie together polymorphic resources with the appropriate settings you want to be controlled.
One possibility is to build a new model that belongs_to the resources that should be affected by those settings.
Will need to expose in the views as appropriate.
Consider what it would mean to edit the resource and change those settings after comments and/or reactions had already been aggregated. Should you show the existing ones or should they all be cut off or should that be a choice for the user?
The text was updated successfully, but these errors were encountered:
Some users would like to turn comments and/or reactions on or off on a per-status or per-post level. Potentially allow that to be set on each individual resource. Investigate how to do that.
One possibility is to add those settings to each individual resource.
One possibility is to use a join table to tie together polymorphic resources with the appropriate settings you want to be controlled.
One possibility is to build a new model that belongs_to the resources that should be affected by those settings.
Will need to expose in the views as appropriate.
Consider what it would mean to edit the resource and change those settings after comments and/or reactions had already been aggregated. Should you show the existing ones or should they all be cut off or should that be a choice for the user?
The text was updated successfully, but these errors were encountered: