Customer extension navigation API doc is wrong

Extensions
1

Hello!

Lost a good day because of that documentation for the navigation API:

All the examples on this page mentions that the custom protocol for extension navigation and cross extension navigation is extension:// for within extension navigation and extension://<handle> for cross extension. It even shows examples with these patterns which don’t work.

It turns out that the correct pattern is mentioned in the main overview page: Customer account UI extensions

The real pattern is supposed to be extension:<handle> for cross extension navigation and we’re supposed to use relative paths for navigation within an extension.

3

Hey @Tommy_Gaudreau :waving_hand: thanks for flagging this. Losing a day to incorrect examples is a meaningful impact on your development time.

We’ve confirmed that the Navigation API documentation is incorrect and that the working syntax you shared is correct. We’re working on correcting the affected documentation and examples, and I’ll follow up here once the changes are live.

Thanks again for catching and documenting the discrepancy.