activationConditionRef problem

[Cantor, Scott]

On 7/9/15, 10:56 AM, "dev on behalf of Rod Widdowson" <dev-bounces at shibboleth.net on behalf of rdw at steadingsoftware.com> wrote:

>Ah, so "https://whatever" becomes "Boolean.false" becomes
>"Predicate.ALWAYS_FALSE"?

Yes. Of course, we could throw an error on such a case, seems like that might be worth doing here.

>Given that the c_0="{{'foo'}}" is easy I'd be inclined to leave this as is.
>But if it is liable to trick more people perhaps we should add a third
>constructor which takes a String; that would override all the conversions.
>This means that c_0="true" would stop falling into the predicate case, but
>I'm not sure that that is obvious in this case.

Since we have time to work on this, let's file a bug and we'll consider the best choice.

-- Scott