On Thu, Jul 14, 2011 at 6:43 AM, Francis J. Lacoste
<email address hidden> wrote:
> I'd rather suggest a boolean feature flag and then we use a custom scope
> selector.
+1
> The scope handler (project:?) could take a comma list of
> project names.
I'd start with (perhaps pillar:) taking just one name and use multiple
rules to represent multiple things. Its what we've done for pageids
etc, and I don't think we'll be overwhelmed with projects wanting it
before we go full-on || option-in-project-config.
> That way we don't need custom flag parsing logic in the feature, and we
> have a reusable feature scope!
On Thu, Jul 14, 2011 at 6:43 AM, Francis J. Lacoste
<email address hidden> wrote:
> I'd rather suggest a boolean feature flag and then we use a custom scope
> selector.
+1
> The scope handler (project:?) could take a comma list of
> project names.
I'd start with (perhaps pillar:) taking just one name and use multiple in-project- config.
rules to represent multiple things. Its what we've done for pageids
etc, and I don't think we'll be overwhelmed with projects wanting it
before we go full-on || option-
> That way we don't need custom flag parsing logic in the feature, and we
> have a reusable feature scope!
\o/