Skip to content

Java render-helper-conformance has no xpkg-collision (ADR-0041) coverage #220

Description

@dmealing

Context

Discovered while reviewing #389255c57 (fix(csharp): payload-generator resolves bare @payloadRef in a named package) and auditing cross-port conformance coverage of fixtures/template-output-render-conformance/.

Every other port that runs this shared corpus exercises the xpkg-collision/ sub-corpus (ADR-0041 cross-package short-name @objectRef resolution — DigestDoc over two colliding Note VOs in different packages):

Java's GeneratedRenderHelperConformanceTest.java (server/java/codegen-spring/src/test/java/com/metaobjects/generator/spring/) has zero references to xpkg, Digest, or DigestDoc. Its coverage stops at document/email/XSS/nested-OrderEmail/drift — the FQN-exact nested @objectRef resolution gate (ADR-0041) is not exercised at all for the Java/Spring port.

Ask

Add the xpkg-collision/ case to Java's render-helper-conformance suite, following the pattern the other 4 ports already use (load meta.alpha.json + meta.beta.json + meta.app.json, generate+compile the DigestDoc render helper, assert FQN-exact resolution binds each ref to its own package). This closes a real cross-port parity gap, independent of the payloadRef bug in #389255c57.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions