Sounds good mate. I look forward taking a look at it
On 11/21/08, Jon Hancock <[EMAIL PROTECTED]> wrote:
>
> My goal is to publish a sample app for learning merb beyond the basic
> docs. In this vein, I want clear code for the merb newb as opposed to
> highly factored and configurable slice code. I suppose if this sample
> app matures enough, either me or someone else could make it a slice.
> I am from the school of "something must have at least three examples
> of abstraction/reuse prior to creating an abstraction". I think its
> best to allow the sample app the mature before trying to create a
> slice for it.
>
> What I am doing is cleaning up my shellshadow.com app which I hope to
> relaunch with merb 1.0 very soon. Then extracting a meaningful subset
> of the code to publish on github as a sample app.
>
> Jon
>
> On Nov 21, 3:19 pm, "Daniel N" <[EMAIL PROTECTED]> wrote:
>> On 11/21/08, Jon Hancock <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>> > ok, thanks for confirming. I'll add it to lighthouse.
>> > btw, I have a fully functional user and session system now leveraging
>> > your slice. Its testing out very well so far. My user model is of
>> > moderate maturity (registration confirm, email address change and
>> > confirmations, password resets, etc.). I intend to extract a sample
>> > app and publish in a week or two.
>> > Jon
>>
>> Cool man that's ace. Will you be extracting as a slice?
>>
>> > On Nov 20, 9:37 pm, "Daniel N" <[EMAIL PROTECTED]> wrote:
>> >> On Thu, Nov 20, 2008 at 4:54 PM, Jon Hancock <[EMAIL PROTECTED]>
>> >> wrote:
>>
>> >> > I'm trying to filter the password from merb log.
>> >> > Since MerbAuthSlicePassword::Sessions doesn't inherit from my app
>> >> > Application controller, I add the following to class
>> >> > MerbAuthSlicePassword::Sessions in slices/merb-auth/app/controller/
>> >> > sessions.rb as follows:
>>
>> >> > class MerbAuthSlicePassword::Sessions <
>> >> > MerbAuthSlicePassword::Application
>>
>> >> > log_params_filtered :password
>>
>> >> > ...
>> >> > end
>>
>> >> > Now my merb log shows the two lines:
>>
>> >> > merb : worker (port 4000) ~ Routed to: {"Submit"=>"Log In",
>> >> > "action"=>"update", "_method"=>"put",
>> >> > "controller"=>"merb_auth_slice_password/sessions",
>> >> > "password"=>"my_cleartext_password",
>> >> > "email"=>"[EMAIL PROTECTED]"}
>>
>> >> > merb : worker (port 4000) ~ Params: {"Submit"=>"Log In",
>> >> > "_method"=>"put", "action"=>"update",
>> >> > "controller"=>"merb_auth_slice_password/sessions",
>> >> > "password"=>"[FILTERED]", "email"=>"[EMAIL PROTECTED]"}
>>
>> >> > Notice the first log output ("~ Routed to:") shows the password and
>> >> > the second output (the "~ Params:") properly filters.
>> >> > This doesn't appear to be a bug in the slice but in merb or the
>> >> > logging.
>>
>> >> > Have I done something wrong or this a bug? This is in development
>> >> > mode with logging to console as is configured by a default "merb-gen
>> >> > app" structure.
>>
>> >> > thanks, Jon
>>
>> >> Hey Jon,
>>
>> >> This is how I would use the protected params plugin. I'm surprised
>> >> that
>> >> this is happening :(
>>
>> >> I'd be interested to find out what the issue is here :(
>>
>> >> Cheers
>> >> Daniel
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
