Yehuda, this is what I was hoping to do. However, after reading through all 4 gems (ok, ones just a meta-gem) and playing with it for a full day, I just gave up. It shouldn't be so hard to know which parts to opt out.
>From what I can tell, the slice should be able to be refactored to enable less or no "opinions" about the internals of my User model and also should easily allow me to specify which view template to use for the login form. As for default behavior, I feel the slice should do nothing to my User model unless I explicitly "opt-in" for some magic. Additionally having a config param for setting the login form template should be easy to add to the current slice code. Without these refactorings, I either have to: 1 - monkeypatch, 2- learn to write my own slice, or 3- cobble together my own solution from auth-core and auth-more. I just feel the new auth structure is close to being a "one-size-fits- all" but still needs a bit of refactoring to get to that point. Hopefully my input will help get it there ;). thanks, Jon On Oct 29, 1:37 am, "Yehuda Katz" <[EMAIL PROTECTED]> wrote: > The Merb philosophy is of granular opt-out. You should always be able to out > of the small part of a component that you don't like without having to roll > the entire thing yourself. > -- Yehuda > > On Tue, Oct 28, 2008 at 10:35 AM, Julian Leviston <[EMAIL PROTECTED]>wrote: > > > > > Ah. > > What is it? > > > Julian. > > > On 29/10/2008, at 4:33 AM, Yehuda Katz wrote: > > > Whoa whoa whoa. > > The Merb philosophy is *not* that if a little part of a component doesn't > > work you should "roll your own". If that's truly the case, it's a mistake on > > our part that requires a correction. > > > -- Yehuda > > > On Tue, Oct 28, 2008 at 10:27 AM, Ahsan Ali <[EMAIL PROTECTED]> wrote: > > >> Simply, don't use merb-auth-password-slice. Refer the READMEs inside > >> merb-auth-core and -more directories to implement your own stuff. > >> -auth-more > >> and -auth-password-slice are optional. > > >> - highandwild > > >> On Tue, Oct 28, 2008 at 9:13 PM, Jon Hancock <[EMAIL PROTECTED]>wrote: > > >>> I have studied the latest 0.9.10 merb-auth, merb-auth-core, merb-auth- > >>> more, and merb-auth-password-slice. > > >>> I'm still confused as to how to get this to work for me. > > >>> The docs tell me that this new auth structure only authenticates > >>> sessions and has not preference to how I write the auth logic. > >>> However, the auth-password-slice goes forward and adds salt and > >>> crypt_password fields to my User model. Its even so presumptuous as > >>> to see that I have datamapper running and use the dm form of injecting > >>> properties. I absolutely do not want this kind of magic going on in > >>> my app. > > >>> So the first question is: > > >>> 1 - How do I get the slice to keep its hands off my User model? What > >>> I want is a simple list of methods that my User should implement and I > >>> will implement those. The docs indicate that this is what I should be > >>> able to do, but the real world default behavior is different. > > >>> 2 - How do I tell this auth framework which erb file I want to use for > >>> my login form? The slice has its own forms. I do not want to pass > >>> lots of config directives to get the form to look almost correct. I > >>> want to completely replace the form and I want to do so without > >>> monkeypatching the slice. How do I do this? > > >>> thanks, Jon > > > -- > > Yehuda Katz > > Developer | Engine Yard > > (ph) 718.877.1325 > > -- > Yehuda Katz > Developer | Engine Yard > (ph) 718.877.1325 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
