+1 to both.
Regards
Felix
Am 22.01.2014 um 16:34 schrieb Carsten Ziegeler :
> Great, I'm fine with this - I just want to make sure that we're all on the
> same page :)
>
> Carsten
>
>
> 2014/1/22 Bertrand Delacretaz
>
>> On Wed, Jan 22, 2014 at 4:05 PM, Carsten Ziegeler
>> wrote:
>>> ...Fi
Great, I'm fine with this - I just want to make sure that we're all on the
same page :)
Carsten
2014/1/22 Bertrand Delacretaz
> On Wed, Jan 22, 2014 at 4:05 PM, Carsten Ziegeler
> wrote:
> > ...Final question, is this still an OR then? So if you have ["-A", "-B"]
> or
> > ["-A", "B"] what doe
On Wed, Jan 22, 2014 at 4:05 PM, Carsten Ziegeler wrote:
> ...Final question, is this still an OR then? So if you have ["-A", "-B"] or
> ["-A", "B"] what does it mean?...
I think we agree on OR so to me
[-A, -B] means "this resource is visible if feature A is disabled OR
feature B is disabled.
Great, thanks, yeah I'm fine with "-"
Final question, is this still an OR then? So if you have ["-A", "-B"] or
["-A", "B"] what does it mean?
Carsten
2014/1/22 Felix Meschberger
> Hi
>
> I am ok, this is easy to implement and I am fine with using "-" as the
> indicator — we also use that pref
Hi
I am ok, this is easy to implement and I am fine with using "-" as the
indicator — we also use that prefix to indicate URLs which don't need
authentication (AuthConstants.AUTH_REQUIREMENTS).
Regards
Felix
Am 22.01.2014 um 15:04 schrieb Carsten Ziegeler :
> @Felix, wdyt?
>
> Carsten
>
>
@Felix, wdyt?
Carsten
2014/1/21 Bertrand Delacretaz
> Hi,
>
> On Tue, Jan 21, 2014 at 2:38 AM, Carsten Ziegeler
> wrote:
> > ...Can we get some consensus, whether we need to specify that a resource
> is
> > hidden if a feature is enabled?...
>
> We need this to implement the "Alternate betwee
Hi,
On Tue, Jan 21, 2014 at 2:38 AM, Carsten Ziegeler wrote:
> ...Can we get some consensus, whether we need to specify that a resource is
> hidden if a feature is enabled?...
We need this to implement the "Alternate between resources based on
feature flags" use case described at
https://cwiki.a
Can we get some consensus, whether we need to specify that a resource is
hidden if a feature is enabled?
The use case I heard of, is that e.g. a button/link(navigation entry is
switched depending whether the feature is available. If it's available
button A is rendered, if not button B - this could
I'm fine with using OR and not going up the hierarchy to see whether a
parent is hidden.
Carsten
2014/1/20 Bertrand Delacretaz
> Hi,
>
> On Mon, Jan 20, 2014 at 9:35 AM, Felix Meschberger
> wrote:
> > Am 20.01.2014 um 04:19 schrieb Carsten Ziegeler :
> >>... It seems we have use cases, like A
Hi,
On Mon, Jan 20, 2014 at 9:35 AM, Felix Meschberger wrote:
> Am 20.01.2014 um 04:19 schrieb Carsten Ziegeler :
>>... It seems we have use cases, like A-B testing where you want to hide a
>> resource if a feature is enabled..
>> ...We can easily implement this with negating the value, like
>> !
Hi
Am 20.01.2014 um 04:19 schrieb Carsten Ziegeler :
> If the sling:features property contains a single string value, this
> resource is only visible if the feature is enabled. This is pretty straight
> forward.
Yes
> It seems we have use cases, like A-B testing where you want to hide a
> resou
If the sling:features property contains a single string value, this
resource is only visible if the feature is enabled. This is pretty straight
forward.
It seems we have use cases, like A-B testing where you want to hide a
resource if a feature is enabled, so A is enabled and B is hidden if the
fea
12 matches
Mail list logo
