feat: Add areaAsSubNode param for Area

[gflores-jahia]

Description

Expose areaAsSubNode param for Area template that is available in the AreaTag jsp template https://github.com/Jahia/jahia-private/blob/master/taglib/src/main/java/org/jahia/taglibs/template/include/AreaTag.java#L113

This allow areas to be distinctly defined within (multiple) declared component when areaAsSubNode is set to true, rather than shared under current page.

Checklist

Source code

• I've shared and documented any breaking change
• I've reviewed and updated the jahia-depends

Tests

• I've provided Unit and/or Integration Tests
• I've updated the parent issue with required manual validations

Tip

Documentation to guide the reviews: How to do a code review

[github-actions]

🦜 Chachalog

javascript-modules minor

• Added an areaAsSubNode option to the Area component similar to template:area jsp tag so repeated components can store area content separately (feat: Add areaAsSubNode param for Area #660)

Create a new entry online or run npx chachalog@0.5.0 prompt to create a new entry locally.

[Copilot]

Pull request overview

Adds support for an areaAsSubNode parameter on the React Area component so areas can be stored under the component node (useful for repeatable components), and introduces E2E coverage for the new behavior.

Changes:

• Add areaAsSubNode prop to Area and forward it to the server render call.
• Allow areaAsSubNode as a permitted attribute in the Java render helper for areas.
• Extend the test component and add a Cypress E2E suite to validate rendering and node placement/isolation.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
tests/cypress/e2e/ui/areaAsSubNodeTest.cy.ts	New E2E coverage for rendering + content isolation/node structure when using areaAsSubNode.
javascript-modules-library/src/components/Area.tsx	Introduces areaAsSubNode prop and forwards it to server.render.renderArea.
javascript-modules-engine-java/.../RenderHelper.java	Adds areaAsSubNode to the allowed attribute whitelist for renderArea.
jahia-test-module/.../TestAreas.tsx	Adds UI fixtures (two Areas) to exercise areaAsSubNode true/false in tests.

[gflores-jahia]

Note that there is an issue rendering areaAsSubNode in this story https://github.com/Jahia/jahia-private/issues/4888, so will need to wait for that before merging this in. Update: This has been recently merged and should be available in latest 8.2.4-SN.

This PR fix and cypress tests has been tested as working on 8.2.2.1 env.

[gflores-jahia]

Fix for https://github.com/Jahia/jahia-private/issues/4888 has been merge and added tests for this PR is now passing.

[Copilot]

Pull request overview

This PR exposes the areaAsSubNode flag on the React <Area /> component so area content can be stored under each component instance (instead of being shared under the page), aligning the JS modules behavior with Jahia’s existing AreaTag capability.

Changes:

• Added areaAsSubNode prop to javascript-modules-library’s <Area /> and forwarded it to server-side rendering.
• Whitelisted areaAsSubNode in the Java engine RenderHelper attribute validation for renderArea.
• Added a test component view + Cypress e2e coverage and a changelog entry.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
tests/cypress/e2e/ui/areaAsSubNodeTest.cy.ts	Adds e2e checks for rendering and node creation paths for areas with/without areaAsSubNode.
javascript-modules-library/src/components/Area.tsx	Introduces the areaAsSubNode prop and passes it to server.render.renderArea.
javascript-modules-engine-java/src/main/java/.../RenderHelper.java	Allows areaAsSubNode through the renderArea attribute whitelist.
jahia-test-module/src/react/server/views/testAreas/TestAreas.tsx	Adds two rendered Areas to exercise areaAsSubNode=true/false in the test module.
.chachalog/bnO8G4QV.md	Documents the addition as a minor change in javascript-modules.

[GauBen]

From slack:

We intentionally removed areaAsSubNode during the beta of JS modules because one of the two values (IIRC areaAsSubNode={false}) does not make sense and we should be using <AbsoluteArea> instead (which does that and more)

That's a shame, reading https://github.com/Jahia/jahia-private/issues/4894 it seems it is implemented as a hardcoded areaAsSubNode={false}

However, the proposed API <Area name="main" parent={currentNode} /> is exactly the one of <AbsoluteArea> (i.e. you attach your area to an explicit node)

• it unconditionally enables page-inheritance regardless of context
• it requires the parent node to already exist in the JCR
• these are broader side-effects absent from JSP's areaAsSubNode

I don't understand these arguments, I never experienced any of these issues

[gflores-jahia]

Thank you for the context. Will check with Philippe to understand why AbsoluteArea does not work when it should be the same as <Area name="main" parent={currentNode} />

Also from David's comment:

FYI areaAsSubNode has been introduce to fix a bug/flaw related to area names, ensure we don't reintroduce it https://support.jahia.com/browse/SOC-121