Not sure if this should be a stable blocker, or if this should happen at all, but the two recipes we provide that use inputs (Google Analytics, and AI) would not work for people using older versions of Project Browser, outside of Drupal CMS. They would not be able to apply these recipes, even if they could see them in Project Browser, since the ability to apply input-bearing recipes in the UI was only added in alpha7.
IMHO it would make sense, as a safeguard, for these recipes to conflict with any version of Project Browser older than 2-alpha7. The only reason this is necessary is because we've promised that our recipes will work on existing sites, and we should probably have constraints which ensure we deliver on that promise.
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
phenaproximaComment #4
phenaproximaComment #5
thejimbirch commentedMakes perfect sense and the code looks good. Marking as RTBC assuming the tests will turn green.
Comment #6
phenaproximaThanks @thejimbirch! I'd like Pam's sign-off on this one, I think, just in case I'm missing something obvious.
Comment #7
pameeela commentedMakes sense to me.
Comment #8
phenaproximaComment #11
phenaproximaThanks for the input (har har) and sanity check :) Merged into 1.x and ported to 1.0.x.