Observers will be removed from rails 4, but will be possible use them with
gem
2012/12/5 Svoop <sven.schwyn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Hiya
>
> No more observers in Rails 4, farewell, never been much of a fan anyway.
>
> However, one of my gems is enabling model attributes for use with a
> client-side WYSIWYM editor. The sanitized markup ends up in the database
> and has to be processed before shown in a view. The corresponding helper
> does fragment caching. This cache has to be zapped when the model is
> modified or deleted. And since the gem is generic, an observer for
> "after_update" "after_destroy" seemed the obvious
choice for this.
>
> What would be the Rails 4 state of the art approach do do this without
> using observers? Inject the above callbacks into the model directly?
>
> -sven
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Talk" group.
> To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To unsubscribe from this group, send email to
>
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> https://groups.google.com/d/msg/rubyonrails-talk/-/PjOT5x0UFSkJ.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
Rodrigo Mendonça
(62) 8567-3142
--
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.