About testing and liftrules, you cannuse the liftrules mock to change it as
you wish in your tests (We can start a thread on the list about that if you
want)

Sent from my tablet
Diego
On Jul 1, 2013 9:09 AM, "David Barri" <notifications@github.com> wrote:

> In
> core/util/src/main/scala/net/liftweb/util/PropertyWithModificationCondition.scala:
>
> > @@ -0,0 +1,28 @@
> > +package net.liftweb.util
> > +
> > +/**
> > + * A property that can be modified under limited conditions.
> > + */
> > +abstract class PropertyWithModificationCondition[T](initialValue: T) {
>
> I'm not sure. I'm still relatively new to Lift but my thought-process was
> this: I'm seeing lots of settings (esp. LiftRules) that live in singletons.
> For runtime you just set them once in Boot and it's happy days but when it
> comes to testing, there've been a few cases I've run into where the
> singleton settings will initialise before a test can change a needed
> setting. Easy to fix once you're aware of it, but the problem I had was I'm
> not always aware of it and sometimes it can take a while to pinpoint the
> problem. I was thinking if we could let the user know when attempting to
> set a property that it's futile, it would save effort.
>
> By RunModeProperty do you mean just adding something like
> warnIfRunModeInitialised() and getting rid of
> PropertyWithModificationCondition?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/lift/framework/pull/1466/files#r4961270>
> .
>