Skip to content

[ECP-9911] Append Magento edition to externalPlatform.name in applicationInfo#3259

Merged
shubhamk67 merged 2 commits intomainfrom
ECP-9911
Mar 3, 2026
Merged

[ECP-9911] Append Magento edition to externalPlatform.name in applicationInfo#3259
shubhamk67 merged 2 commits intomainfrom
ECP-9911

Conversation

@shubhamk67
Copy link
Contributor

Description
Magento/Adobe Commerce has different application editions (Community, Enterprise, etc.). This change appends the edition to the externalPlatform.name field sent in applicationInfo to Adyen, so the name will now be "Magento Community" or "Magento Enterprise" instead of just "Magento".

@shubhamk67 shubhamk67 requested a review from a team as a code owner February 24, 2026 16:27
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @shubhamk67, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the platform information sent to Adyen by incorporating the specific Magento edition into the platform name. This enhancement allows Adyen to receive more precise details about the originating Magento environment, which can be beneficial for reporting, analytics, and tailored service offerings, without altering the core functionality of the payment processing.

Highlights

  • Enhanced Platform Identification: The Magento edition (e.g., Community, Enterprise) is now appended to the externalPlatform.name field within applicationInfo when communicating with Adyen. This provides more granular detail about the Magento environment.
  • Consistent Data Reporting: This change ensures that both standard Adyen client requests and Point of Sale (POS) requests send the complete platform name, including the edition, for improved data consistency and analytics.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • Helper/Data.php
    • Appended the Magento edition to the platform name before setting it in the Adyen client's external platform information.
  • Helper/PointOfSale.php
    • Modified the SaleToAcquirerData generation to include the Magento edition in the external platform name for Point of Sale requests.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request successfully appends the Magento edition to the external platform name in applicationInfo, which aligns with the stated goal. The changes are clear and address the requirement. However, there's a minor improvement opportunity to ensure that an extra space is not added if the edition string is empty, which could lead to inconsistent naming.

$platformIntegratorName = $this->configHelper->getPlatformIntegratorName();
$platformIntegrator = ($hasPlatformIntegrator && $platformIntegratorName) ? $platformIntegratorName : '';
$client->setExternalPlatform($platformData['name'], $platformData['version'], $platformIntegrator);
$platformName = $platformData['name'] . ' ' . $platformData['edition'];
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To prevent an extra space from appearing in platformName if $platformData['edition'] is empty, consider using trim() around the concatenated string. This ensures a clean output regardless of whether an edition is present.

$platformName = trim($platformData['name'] . ' ' . $platformData['edition']);

[ApplicationInfo::VERSION] = $this->productMetadata->getVersion();
$saleToAcquirerData[ApplicationInfo::APPLICATION_INFO][ApplicationInfo::EXTERNAL_PLATFORM]
[ApplicationInfo::NAME] = $this->productMetadata->getName();
[ApplicationInfo::NAME] = $this->productMetadata->getName() . ' ' . $this->productMetadata->getEdition();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Similar to the Helper/Data.php file, if getEdition() returns an empty string, this concatenation will result in an unnecessary trailing space. Using trim() will ensure the string is correctly formatted in all cases.

[ApplicationInfo::NAME] = trim($this->productMetadata->getName() . ' ' . $this->productMetadata->getEdition());

@sonarqubecloud
Copy link

@shubhamk67 shubhamk67 merged commit 15aade0 into main Mar 3, 2026
9 of 10 checks passed
@shubhamk67 shubhamk67 deleted the ECP-9911 branch March 3, 2026 11:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants