Frontmatter
| title | Add RMA helper utilities |
| author | Aki-07 |
| state | Merged |
| createdAt | Oct 11, 2025, 7:19 AM |
| updatedAt | Oct 11, 2025, 11:06 AM |
| closedAt | Oct 11, 2025, 10:40 AM |
| mergedAt | Oct 11, 2025, 10:40 AM |
| branches | dev ← feat/component-rma-helpers |
| url | https://github.com/neomjs/neo/pull/7459 |

Thanks for your contribution, accepted. I will do some minor changes afterwards. Input from Gemini:
✦ PR Review: ticket-create-rma-test-helpers
This is a fantastic first contribution, thank you so much! It's a huge help in getting our new Playwright test suite off the ground. The implementation is clean and very close to perfect.
To make your first contribution as smooth as possible, we're going to merge this PR as is and handle a couple of minor polishing items ourselves. We wanted to share the details with you for future reference:
- Functional Detail in
getComponentConfig: The remote method Neo.worker.App.getConfigs() expects its payload to be an object with a keys property. The current implementation sends keyOrKeys instead, which would prevent it from working as expected.* Current Code in `test/playwright/util/RmaHelpers.mjs`:1 async getComponentConfig(id, keyOrKeys) { 2 return Neo.worker.App.getConfigs({ 3 id, 4 keyOrKeys // This property should be named 'keys' 5 }); 6 }, * Required Change:
1 async getComponentConfig(id, keyOrKeys) { 2 return Neo.worker.App.getConfigs({ 3 id, 4 keys: keyOrKeys // Renaming the property to 'keys' 5 }); 6 },
- Style Detail (Filename Casing): The ticket suggested the filename rma-helpers.mjs (kebab-case), while the PR uses RmaHelpers.mjs (PascalCase). We'll rename the file to align with the conventions of other utility scripts in that directory.
Again, these are very minor points. We'll take care of them.
Excellent work, and we're thrilled to have you contributing to the project. We look forward to your next PR! Welcome to the Neo.mjs team.
Please make sure to read the Contributing Guidelines:
https://github.com/neomjs/neo/blob/dev/CONTRIBUTING.md
Fixes #7438 What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
devbranch, not themainbranchfix #xxx[,#xxx], where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Summary