Akeneo - fix async options for Attribute Code

[michelle0927]

Resolves #17164

Summary by CodeRabbit

• Bug Fixes
  • Improved handling of search filters for media file attribute types, ensuring more accurate filtering when selecting image attributes.
• Chores
  • Updated version numbers to 0.1.1 for consistency across the action and package.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
docs-v2	⬜️ Ignored (Inspect)			Jun 25, 2025 5:21pm
pipedream-docs	⬜️ Ignored (Inspect)			Jun 25, 2025 5:21pm
pipedream-docs-redirect-do-not-edit	⬜️ Ignored (Inspect)			Jun 25, 2025 5:21pm

[coderabbitai]

Walkthrough

The changes update the version numbers in the Akeneo package and its action, and modify the construction of the search parameter in the mediaFileAttributeCode prop's options method to use a JSON string instead of a plain object. No other functional or structural modifications are present.

Changes

File(s)	Change Summary
components/akeneo/actions/create-a-new-product-media-file/create-a-new-product-media-file.mjs	Updated action version from "0.1.0" to "0.1.1".
components/akeneo/akeneo.app.mjs	Changed search parameter in mediaFileAttributeCode's options method to use JSON string.
components/akeneo/package.json	Bumped package version from "0.1.0" to "0.1.1".

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant AkeneoApp
    participant AkeneoAPI

    User->>AkeneoApp: Request options for mediaFileAttributeCode
    AkeneoApp->>AkeneoAPI: getAttributes({ search: JSON.stringify({ type: ["pim_catalog_image"] }) })
    AkeneoAPI-->>AkeneoApp: Return filtered attributes
    AkeneoApp-->>User: Present options

Loading

Assessment against linked issues

Objective	Addressed	Explanation
Fix async options loading for Akeneo action akeneo-create-a-new-product-media-file (#17164)	✅

Poem

A hop and a skip, a version anew,
JSON strings now guide what the options will do.
Akeneo’s choices, once hidden from sight,
Are loading again—oh what a delight!
With numbers that tick and bugs that take flight,
The code hops ahead, all through the night.
🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

components/akeneo/actions/create-a-new-product-media-file/create-a-new-product-media-file.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:201:49)

components/akeneo/akeneo.app.mjs

Oops! Something went wrong! :(

ESLint: 8.57.1

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'jsonc-eslint-parser' imported from /eslint.config.mjs
at Object.getPackageJSONURL (node:internal/modules/package_json_reader:255:9)
at packageResolve (node:internal/modules/esm/resolve:767:81)
at moduleResolve (node:internal/modules/esm/resolve:853:18)
at defaultResolve (node:internal/modules/esm/resolve:983:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:801:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
at #link (node:internal/modules/esm/module_job:201:49)

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between db67e3d and 7526019.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (3)

• components/akeneo/actions/create-a-new-product-media-file/create-a-new-product-media-file.mjs (1 hunks)
• components/akeneo/akeneo.app.mjs (2 hunks)
• components/akeneo/package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: Verify TypeScript components
• GitHub Check: pnpm publish
• GitHub Check: Publish TypeScript components
• GitHub Check: Lint Code Base

🔇 Additional comments (3)

components/akeneo/package.json (1)

3-3: LGTM! Appropriate version bump for bug fix.

The patch version increment from "0.1.0" to "0.1.1" correctly follows semantic versioning practices for a bug fix.

components/akeneo/akeneo.app.mjs (1)

54-63: Good fix! JSON.stringify() correctly formats the search parameter.

This change addresses the async options issue by properly serializing the search parameter as a JSON string, which is likely what the Akeneo API expects for complex query parameters.

Please verify that this change resolves the async options issue by testing the mediaFileAttributeCode prop to ensure it correctly fetches and displays image attributes.

#!/bin/bash
# Description: Check if there are any other search parameters in the codebase that might need similar fixes
# Expected: Find other instances of search parameters that might need JSON.stringify()

echo "Searching for other search parameter usage in Akeneo components..."
rg -A 5 -B 5 "search.*:" --type js

components/akeneo/actions/create-a-new-product-media-file/create-a-new-product-media-file.mjs (1)

10-10: LGTM! Version consistency maintained.

The version bump aligns with the package version and ensures consistency across the Akeneo integration components.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[jcortes]

Hi @michelle0927 lgtm! Ready for QA!