Skip to content

Conversation

@robotdad
Copy link
Member

@robotdad robotdad commented Jan 7, 2026

Summary

Bundle namespace references in YAML frontmatter require the @ prefix to resolve correctly. Without it, paths fail to resolve with 'file not found' errors. This PR fixes incorrect examples in the documentation that would have led users to encounter these errors.

Changes

Fixed 7 incorrect examples in docs/BUNDLE_GUIDE.md that showed namespace references without the @ prefix:

  • Lines 74, 103, 167, 252, 393, 556, 615

Added comprehensive 'Namespace Resolution Rules' section explaining:

  • When @ prefix is required (context includes, bundle includes, agents)
  • Correct vs incorrect examples for each pattern
  • Why the @ prefix matters (triggers namespace resolution)

Why This Matters

Users following the documentation examples would encounter 'file not found' errors when trying to use namespace references without the @ prefix. This fix ensures all examples in the guide are accurate and will work correctly when used.

Related

This fix was identified while working on using recipes in a bundle, see:

There is another closed PR where a docstring was updated to emphasize the @ notation for recipes which might be a good idea as well.

Test Plan

  • Verified all corrected examples now use proper @ prefix syntax
  • Reviewed Namespace Resolution Rules section for accuracy
  • Confirmed changes align with actual namespace resolution behavior

🤖 Generated with Amplifier

Co-Authored-By: Amplifier 240397093+microsoft-amplifier@users.noreply.github.com

Bundle namespace references in YAML frontmatter require the @ prefix
to resolve correctly. Without it, paths fail to resolve with 'file not
found' errors.

Fixed 7 incorrect examples in BUNDLE_GUIDE.md that showed namespace
references without the @ prefix:
- Lines 74, 103, 167, 252, 393, 556, 615

Added comprehensive 'Namespace Resolution Rules' section explaining:
- When @ prefix is required (context includes, bundle includes, agents)
- Correct vs incorrect examples for each pattern
- Why the @ prefix matters (triggers namespace resolution)

Related: DavidKoleczek/amplifier-expert-cookbook@94ee8bf

This issue was discovered while setting up a bundle with recipes in a
subdirectory. The recipe path resolution failed until @ prefix was added.
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.

1 participant