I was thinking about how to best extend the session for a plug-in, so I had a look at merb-auth-core (0.9.9).
It opens up Merb::Session and defines a self.included method. That seems dangerous (and in this case completely unnecessary) to me. If I do the same in my plug-in one will overwrite the other. What am I missing? And also, for its helper, it does this: Merb::Controller.send(:include, Merb::AuthenticatedHelper) How is that preferable to opening up Merb::GlobalHelpers and adding your methods there? Forcing an include into Merb::Controller feels a little like bypassing the public API, no? (I've been away from Ruby for a number of years, mostly living in Erlang-land, and have forgotten many Ruby idioms, so I apologize if I'm off base here.) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
