Understand how FeraRender compares friendly placeholder names.

Overview

Understand how FeraRender compares friendly placeholder names. Dataset and mapping work defines the contract between application data and template content. Stable names and representative samples reduce downstream breakage.

Key points

• Comparison removes spaces, periods, underscores, and hyphens.
• Comparison is case-insensitive.
• The original placeholder remains the author-facing name.
• Avoid defining multiple placeholders that normalize to the same value.
• Use stable dotted names for readability.

Recommended procedure

1. Start with representative source data.
2. Define or inspect the dataset tree.
3. Create explicit placeholder-to-XPath mappings.
4. Scan, validate, and test the affected template with missing and repeated values.

Troubleshooting

Validation reports MAPPING_REQUIRED

Create a mapping for every unresolved placeholder and run validation again.

A mapping resolves the wrong field

Look for normalized-name collisions and verify the XPath against sample XML.

An array field is missing from the inferred tree

Use representative sample data with at least one complete array item.

Related documentation

• Resolve Missing Field Mappings
• Map Friendly Placeholders to XPath
• Validate and Browse a Dataset

Documentation source: feradelinc/feradel.render.api, reviewed against repository revision b2c3a710. Verify behavior against the deployed release before publishing exact routes, limits, or version requirements.