[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CST4YNZ717YBZ5AFFYFH6C":3,"skill-same:01M6CST4YNZ717YBZ5AFFYFH6C":76},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":14,"repositoryHtmlUrl":57,"repositoryHomepageUrl":58,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6CST4YNZ717YBZ5AFFYFH6C","api-platform:make-processor",null,"Génère un State Processor API Platform pour personnaliser la persistence des données","atournayre\u002Fclaude-personas","atournayre","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4262077?v=4","01M6CSSGYW0E0D0M3E2T6J9X2Z","Aurélien Tournayre","01M6CSSH3DENJF2XWZ41H0F43K",0,"MIT","https:\u002F\u002Fgithub.com\u002Fatournayre\u002Fclaude-personas\u002Fblob\u002Fmain\u002Fapi-platform\u002Fskills\u002Fmake-processor\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38],"processor","api","api platform:make processor","state","persistence","Bash","grep","read","write","edit","2026-11-10 10:12:30",false,"---\nname: api-platform:make-processor\ndescription: Génère un State Processor API Platform pour personnaliser la persistence des données\nargument-hint: \u003Cnom-resource>\nmodel: sonnet\nallowed-tools: [AskUserQuestion, Bash, Read, Write, Edit, Grep, Glob]\nversion: 1.0.0\nlicense: MIT\n---\n\n# API Platform Make Processor\n\nGénère un State Processor personnalisé pour API Platform. Les processors sont responsables de la persistence des données pour les opérations d'écriture (POST, PUT, PATCH, DELETE).\n\n## Variables\n- **{ResourceName}** - Nom de la resource en PascalCase\n- **{namespace}** - Namespace du projet (défaut: App)\n\n## Outputs\n- `src\u002FState\u002F{ResourceName}Processor.php`\n\n## Instructions à Exécuter\n\n**IMPORTANT : Exécute ce workflow étape par étape :**\n\n### 1. Identifier la resource cible\n\n- Si `$ARGUMENTS` est fourni, utiliser comme nom de la resource\n- Sinon, utiliser AskUserQuestion :\n  ```\n  Question: \"Pour quelle resource créer un State Processor ?\"\n  Header: \"Resource\"\n  ```\n\n### 2. Vérifier la resource existante\n\n- Chercher `src\u002FEntity\u002F{ResourceName}.php` ou `src\u002FApiResource\u002F{ResourceName}.php` avec Glob\n- Si la resource existe, lire le fichier pour comprendre sa structure\n- Si la resource n'existe pas, informer l'utilisateur\n\n### 3. Choisir la stratégie de processing\n\n- Utiliser AskUserQuestion :\n  ```\n  Question: \"Quelle stratégie de processing ?\"\n  Header: \"Stratégie\"\n  Options:\n    - \"Décorer Doctrine (Recommandé)\" : \"Ajouter de la logique avant\u002Faprès la persistence Doctrine\"\n    - \"Custom complet\" : \"Logique de persistence entièrement personnalisée\"\n    - \"Messenger (async)\" : \"Dispatcher un message Symfony Messenger au lieu de persister directement\"\n  ```\n\n### 4. Identifier les opérations à gérer\n\n- Utiliser AskUserQuestion (multiSelect: true) :\n  ```\n  Question: \"Quelles opérations le processor doit-il gérer ?\"\n  Header: \"Opérations\"\n  Options:\n    - \"Création (POST)\" : \"Logique spécifique à la création de la resource\"\n    - \"Mise à jour (PUT\u002FPATCH)\" : \"Logique spécifique à la modification\"\n    - \"Suppression (DELETE)\" : \"Logique spécifique à la suppression (soft delete, cascade, etc.)\"\n  ```\n\n### 5. Détecter le namespace du projet\n\n- Lire `composer.json` avec Read\n- Extraire le namespace depuis `autoload.psr-4`\n\n### 6. Générer le State Processor\n\n**Processor décorant Doctrine :**\n\n```php\n\u003C?php\n\ndeclare(strict_types=1);\n\nnamespace {namespace}\\State;\n\nuse ApiPlatform\\Metadata\\DeleteOperationInterface;\nuse ApiPlatform\\Metadata\\Operation;\nuse ApiPlatform\\State\\ProcessorInterface;\n\n\u002F**\n * @implements ProcessorInterface\u003C{ResourceName}, {ResourceName}|void>\n *\u002F\nfinal readonly class {ResourceName}Processor implements ProcessorInterface\n{\n    public function __construct(\n        private ProcessorInterface $decorated,\n    ) {\n    }\n\n    public function process(mixed $data, Operation $operation, array $uriVariables = [], array $context = []): mixed\n    {\n        if ($operation instanceof DeleteOperationInterface) {\n            return $this->processDelete($data, $operation, $uriVariables, $context);\n        }\n\n        \u002F\u002F Logique avant persistence\n        $this->beforePersist($data, $operation, $context);\n\n        $result = $this->decorated->process($data, $operation, $uriVariables, $context);\n\n        \u002F\u002F Logique après persistence\n        $this->afterPersist($result, $operation, $context);\n\n        return $result;\n    }\n\n    private function beforePersist(mixed $data, Operation $operation, array $context): void\n    {\n        \u002F\u002F Ex: enrichir les données, valider, auditer\n    }\n\n    private function afterPersist(mixed $result, Operation $operation, array $context): void\n    {\n        \u002F\u002F Ex: envoyer un email, dispatcher un event, invalider un cache\n    }\n\n    private function processDelete(mixed $data, Operation $operation, array $uriVariables, array $context): void\n    {\n        \u002F\u002F Ex: soft delete au lieu de suppression physique\n        $this->decorated->process($data, $operation, $uriVariables, $context);\n    }\n}\n```\n\n**Processor avec Messenger :**\n\n```php\n\u003C?php\n\ndeclare(strict_types=1);\n\nnamespace {namespace}\\State;\n\nuse ApiPlatform\\Metadata\\Operation;\nuse ApiPlatform\\State\\ProcessorInterface;\nuse Symfony\\Component\\Messenger\\MessageBusInterface;\nuse {namespace}\\Message\\Create{ResourceName}Message;\n\n\u002F**\n * @implements ProcessorInterface\u003C{ResourceName}, {ResourceName}>\n *\u002F\nfinal readonly class {ResourceName}Processor implements ProcessorInterface\n{\n    public function __construct(\n        private MessageBusInterface $messageBus,\n    ) {\n    }\n\n    public function process(mixed $data, Operation $operation, array $uriVariables = [], array $context = []): mixed\n    {\n        $this->messageBus->dispatch(new Create{ResourceName}Message($data));\n\n        return $data;\n    }\n}\n```\n\n### 7. Configurer le service (si décoration Doctrine)\n\n- Informer de la configuration :\n\n```yaml\n# config\u002Fservices.yaml\nservices:\n    App\\State\\{ResourceName}Processor:\n        arguments:\n            $decorated: '@api_platform.doctrine.orm.state.persist_processor'\n        # Pour la suppression :\n        # $decorated: '@api_platform.doctrine.orm.state.remove_processor'\n```\n\n### 8. Mettre à jour la resource\n\n- Ajouter le processor dans l'attribut `#[ApiResource]` :\n\n```php\n#[ApiResource(\n    processor: {ResourceName}Processor::class,\n)]\n```\n\n### 9. Afficher le résumé\n\n```\nState Processor {ResourceName}Processor généré\n\nFichiers créés :\n- src\u002FState\u002F{ResourceName}Processor.php\n\nConfiguration requise :\n- Vérifier config\u002Fservices.yaml (si décoration Doctrine)\n\nProchaines étapes :\n- Implémenter la logique métier dans process()\n- Créer le provider associé : \u002Fapi-platform:make-provider {ResourceName}\n- Tester : \u002Fapi-platform:make-test {ResourceName}\n```\n\n## Patterns appliqués\n\n### State Processor\n- Implémente `ProcessorInterface`\n- Classe `final readonly`\n- Séparation create\u002Fupdate\u002Fdelete dans des méthodes dédiées\n- Hook beforePersist\u002FafterPersist pour la logique métier\n\n### Bonnes pratiques\n- Décorer le processor Doctrine pour garder la persistence automatique\n- Utiliser `DeleteOperationInterface` pour détecter les suppressions\n- Dispatcher des events\u002Fmessages pour les effets de bord (emails, notifications)\n- Ne pas mélanger logique métier et persistence dans le même processor\n\n## Notes\n- Le processor est appelé pour les opérations POST, PUT, PATCH, DELETE\n- Pour la lecture (GET), utiliser un State Provider\n- Un processor peut retourner un objet différent de celui reçu (transformation)\n- Pour le traitement asynchrone, combiner avec Symfony Messenger\n","# API Platform Make Processor\n\nGénère un State Processor personnalisé pour API Platform. Les processors sont responsables de la persistence des données pour les opérations d'écriture (POST, PUT, PATCH, DELETE).\n\n## Variables\n- **{ResourceName}** - Nom de la resource en PascalCase\n- **{namespace}** - Namespace du projet (défaut: App)\n\n## Outputs\n- `src\u002FState\u002F{ResourceName}Processor.php`\n\n## Instructions à Exécuter\n\n**IMPORTANT : Exécute ce workflow étape par étape :**\n\n### 1. Identifier la resource cible\n\n- Si `$ARGUMENTS` est fourni, utiliser comme nom de la resource\n- Sinon, utiliser AskUserQuestion :\n  ```\n  Question: \"Pour quelle resource créer un State Processor ?\"\n  Header: \"Resource\"\n  ```\n\n### 2. Vérifier la resource existante\n\n- Chercher `src\u002FEntity\u002F{ResourceName}.php` ou `src\u002FApiResource\u002F{ResourceName}.php` avec Glob\n- Si la resource existe, lire le fichier pour comprendre sa structure\n- Si la resource n'existe pas, informer l'utilisateur\n\n### 3. Choisir la stratégie de processing\n\n- Utiliser AskUserQuestion :\n  ```\n  Question: \"Quelle stratégie de processing ?\"\n  Header: \"Stratégie\"\n  Options:\n    - \"Décorer Doctrine (Recommandé)\" : \"Ajouter de la logique avant\u002Faprès la persistence Doctrine\"\n    - \"Custom complet\" : \"Logique de persistence entièrement personnalisée\"\n    - \"Messenger (async)\" : \"Dispatcher un message Symfony Messenger au lieu de persister directement\"\n  ```\n\n### 4. Identifier les opérations à gérer\n\n- Utiliser AskUserQuestion (multiSelect: true) :\n  ```\n  Question: \"Quelles opérations le processor doit-il gérer ?\"\n  Header: \"Opérations\"\n  Options:\n    - \"Création (POST)\" : \"Logique spécifique à la création de la resource\"\n    - \"Mise à jour (PUT\u002FPATCH)\" : \"Logique spécifique à la modification\"\n    - \"Suppression (DELETE)\" : \"Logique spécifique à la suppression (soft delete, cascade, etc.)\"\n  ```\n\n### 5. Détecter le namespace du projet\n\n- Lire `composer.json` avec Read\n- Extraire le namespace depuis `autoload.psr-4`\n\n### 6. Générer le State Processor\n\n**Processor décorant Doctrine :**\n\n```php\n\u003C?php\n\ndeclare(strict_types=1);\n\nnamespace {namespace}\\State;\n\nuse ApiPlatform\\Metadata\\DeleteOperationInterface;\nuse ApiPlatform\\Metadata\\Operation;\nuse ApiPlatform\\State\\ProcessorInterface;\n\n\u002F**\n * @implements ProcessorInterface\u003C{ResourceName}, {ResourceName}|void>\n *\u002F\nfinal readonly class {ResourceName}Processor implements ProcessorInterface\n{\n    public function __construct(\n        private ProcessorInterface $decorated,\n    ) {\n    }\n\n    public function process(mixed $data, Operation $operation, array $uriVariables = [], array $context = []): mixed\n    {\n        if ($operation instanceof DeleteOperationInterface) {\n            return $this->processDelete($data, $operation, $uriVariables, $context);\n        }\n\n        \u002F\u002F Logique avant persistence\n        $this->beforePersist($data, $operation, $context);\n\n        $result = $this->decorated->process($data, $operation, $uriVariables, $context);\n\n        \u002F\u002F Logique après persistence\n        $this->afterPersist($result, $operation, $context);\n\n        return $result;\n    }\n\n    private function beforePersist(mixed $data, Operation $operation, array $context): void\n    {\n        \u002F\u002F Ex: enrichir les données, valider, auditer\n    }\n\n    private function afterPersist(mixed $result, Operation $operation, array $context): void\n    {\n        \u002F\u002F Ex: envoyer un email, dispatcher un event, invalider un cache\n    }\n\n    private function processDelete(mixed $data, Operation $operation, array $uriVariables, array $context): void\n    {\n        \u002F\u002F Ex: soft delete au lieu de suppression physique\n        $this->decorated->process($data, $operation, $uriVariables, $context);\n    }\n}\n```\n\n**Processor avec Messenger :**\n\n```php\n\u003C?php\n\ndeclare(strict_types=1);\n\nnamespace {namespace}\\State;\n\nuse ApiPlatform\\Metadata\\Operation;\nuse ApiPlatform\\State\\ProcessorInterface;\nuse Symfony\\Component\\Messenger\\MessageBusInterface;\nuse {namespace}\\Message\\Create{ResourceName}Message;\n\n\u002F**\n * @implements ProcessorInterface\u003C{ResourceName}, {ResourceName}>\n *\u002F\nfinal readonly class {ResourceName}Processor implements ProcessorInterface\n{\n    public function __construct(\n        private MessageBusInterface $messageBus,\n    ) {\n    }\n\n    public function process(mixed $data, Operation $operation, array $uriVariables = [], array $context = []): mixed\n    {\n        $this->messageBus->dispatch(new Create{ResourceName}Message($data));\n\n        return $data;\n    }\n}\n```\n\n### 7. Configurer le service (si décoration Doctrine)\n\n- Informer de la configuration :\n\n```yaml\n# config\u002Fservices.yaml\nservices:\n    App\\State\\{ResourceName}Processor:\n        arguments:\n            $decorated: '@api_platform.doctrine.orm.state.persist_processor'\n        # Pour la suppression :\n        # $decorated: '@api_platform.doctrine.orm.state.remove_processor'\n```\n\n### 8. Mettre à jour la resource\n\n- Ajouter le processor dans l'attribut `#[ApiResource]` :\n\n```php\n#[ApiResource(\n    processor: {ResourceName}Processor::class,\n)]\n```\n\n### 9. Afficher le résumé\n\n```\nState Processor {ResourceName}Processor généré\n\nFichiers créés :\n- src\u002FState\u002F{ResourceName}Processor.php\n\nConfiguration requise :\n- Vérifier config\u002Fservices.yaml (si décoration Doctrine)\n\nProchaines étapes :\n- Implémenter la logique métier dans process()\n- Créer le provider associé : \u002Fapi-platform:make-provider {ResourceName}\n- Tester : \u002Fapi-platform:make-test {ResourceName}\n```\n\n## Patterns appliqués\n\n### State Processor\n- Implémente `ProcessorInterface`\n- Classe `final readonly`\n- Séparation create\u002Fupdate\u002Fdelete dans des méthodes dédiées\n- Hook beforePersist\u002FafterPersist pour la logique métier\n\n### Bonnes pratiques\n- Décorer le processor Doctrine pour garder la persistence automatique\n- Utiliser `DeleteOperationInterface` pour détecter les suppressions\n- Dispatcher des events\u002Fmessages pour les effets de bord (emails, notifications)\n- Ne pas mélanger logique métier et persistence dans le même processor\n\n## Notes\n- Le processor est appelé pour les opérations POST, PUT, PATCH, DELETE\n- Pour la lecture (GET), utiliser un State Provider\n- Un processor peut retourner un objet différent de celui reçu (transformation)\n- Pour le traitement asynchrone, combiner avec Symfony Messenger\n",{"name":5,"model":44,"license":15,"version":45,"description":7,"allowed-tools":46,"argument-hint":53},"sonnet","1.0.0",[47,34,48,49,50,51,52],"AskUserQuestion","Read","Write","Edit","Grep","Glob","\u003Cnom-resource>","main","bb0335112ea0991dc1dc6a29fa5a861397a5a6f6","api-platform\u002Fskills\u002Fmake-processor","https:\u002F\u002Fgithub.com\u002Fatournayre\u002Fclaude-personas","https:\u002F\u002Fatournayre.github.io\u002Fclaude-personas\u002F","https:\u002F\u002Fgithub.com\u002Fatournayre","🔵, Back End Developer, @symfony  :heart:, @rectorphp :heart:,  \r\n:bug: fixer (creator sometimes 🤫), member of @afup","2026-03-02 23:42:20",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add atournayre\u002Fclaude-personas --skill \"api-platform:make-processor\"",{"tool":68,"command":69},"bunx","bunx skills add atournayre\u002Fclaude-personas --skill \"api-platform:make-processor\"",{"tool":71,"command":72},"pnpm","pnpm dlx skills add atournayre\u002Fclaude-personas --skill \"api-platform:make-processor\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fatournayre\u002Fclaude-personas\u002Fblob\u002Fmain\u002Fapi-platform\u002Fskills\u002Fmake-processor\u002FSKILL.md",true,[],[77,89,125,132,140,151],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":39},"01M6CSZPR0W1K1S9BX3247CZJ1","twig:make-component","Génère un Twig Component Symfony UX (classe PHP + template Twig)","https:\u002F\u002Fgithub.com\u002Fatournayre\u002Fclaude-personas\u002Fblob\u002Fmain\u002Ftwig\u002Fskills\u002Fmake-component\u002FSKILL.md",[],[84,85,36,38,37,86,35,87,88,34],"twig:make component","component","ux","template","php",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":107,"publishedAt":39},"01M6CSZKCYYT4EAW4CDSTS3TSH","tester:ui-test","Teste automatiquement une interface utilisateur dans Chrome : navigation, clics, validation visuelle, tests fonctionnels, responsive, comportement et debug. Génère un rapport détaillé avec screenshots et optionnellement un GIF du parcours.","https:\u002F\u002Fgithub.com\u002Fatournayre\u002Fclaude-personas\u002Fblob\u002Fmain\u002Ftester\u002Fskills\u002Fui-test\u002FSKILL.md",[95,98,101,104],{"categoryNo":96,"categoryName":97,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":99,"categoryName":100,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":102,"categoryName":103,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":105,"categoryName":106,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师",[108,109,110,111,112,113,114,115,116,117,118,34,119,120,121,122,36,37,123,124],"test","ui","tester","ui test","tester:ui test","MCP","debug","create","update","validation","messages","plan","tool","page","find","javascript","chrome",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":39},"01M6CSZGQ8X9XNXRBYX0AA3CYE","symfony:voter","Genere un Voter de securite Symfony pour le controle d'acces granulaire","https:\u002F\u002Fgithub.com\u002Fatournayre\u002Fclaude-personas\u002Fblob\u002Fmain\u002Fsymfony\u002Fskills\u002Fvoter\u002FSKILL.md",[],[127,34,35,36,37,38],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":39},"01M6CSZEJ3BNHCNZT18SYFGDME","symfony:message","Genere un Message Symfony Messenger avec son Handler pour traitement asynchrone","https:\u002F\u002Fgithub.com\u002Fatournayre\u002Fclaude-personas\u002Fblob\u002Fmain\u002Fsymfony\u002Fskills\u002Fmessage\u002FSKILL.md",[],[134,139,34,35,36,37,38],"message",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":149,"publishedAt":39},"01M6CSZBWSK9M6YMJX886BVWYF","symfony:mailer","Genere un email Symfony (TemplatedEmail ou Notification) avec template Twig","https:\u002F\u002Fgithub.com\u002Fatournayre\u002Fclaude-personas\u002Fblob\u002Fmain\u002Fsymfony\u002Fskills\u002Fmailer\u002FSKILL.md",[146],{"categoryNo":147,"categoryName":148,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通",[142,38,150,34,87,35,36,37],"email",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":39},"01M6CSZ9DXMYZ9HTRE8A324AWG","symfony:form","Genere un FormType Symfony avec contraintes de validation et options","https:\u002F\u002Fgithub.com\u002Fatournayre\u002Fclaude-personas\u002Fblob\u002Fmain\u002Fsymfony\u002Fskills\u002Fform\u002FSKILL.md",[],[153,34,35,36,37,38,158,117],"options"]