Problem/Motivation
The drupal/ai_figma constraint is ^1.0, which still permits 1.0.0. That release carries the AI Context seeding bug fixed in #3621167: AiFigmaInstaller wrote a grouped scope_id => [value, ...] array into the scope field, which drupal/ai_context 1.0.0-beta5 (#3586405) turned into a multi-value scope_id + value field. The resulting InvalidArgumentException was caught and logged as a warning, so the recipe reported success while no AI Context item was ever created.
VarbaseAiFigmaInstaller extends AiFigmaInstaller. Its own seeding path was fixed in #3621159 and released in 1.0.1, but the inherited parent path is fixed only in ai_figma 1.0.1. So a site resolving ai_figma 1.0.0 alongside this module still gets the silent failure.
Steps to reproduce
- Require
drupal/varbase_ai_figma1.0.1 withdrupal/ai_figmapinned to 1.0.0 anddrupal/ai_contextat 1.0.0-beta5 or later. - Apply the recipe. It reports success, the log carries
Could not seed AI Context items, and no AI Context items exist.
Proposed resolution
Raise the constraint to drupal/ai_figma: ^1.0.1 so Composer cannot resolve a version without the fix.
Remaining tasks
- ✅ File an issue
- ✅ Addition/Change/Update/Fix
- ❌ Testing to ensure no regression
- ❌ Reviewed by a human
- ❌ Code review by maintainers
- ❌ Release
User interface changes
- None.
API changes
- None.
Data model changes
- None.
Release notes snippet
- Require
drupal/ai_figma1.0.1 or later, so the AI Context seeding fix cannot be resolved away.
Issue fork varbase_ai_figma-3621172
Show commands
Start 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:
Comments