Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add note about nav target path uniqueness #4070

Open
wants to merge 3 commits into
base: latest
Choose a base branch
from
Open
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions articles/flow/routing/route.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -67,5 +67,8 @@ public class HomeView extends Div {
}
----

[NOTE]
All navigation target paths in the application must be unique to allow Flow to determine the view to render without any disambiguation. This affects all [annotationname]`@Route`, [annotationname]`@RouteAlias` and [annotationname]`@RoutePrefix` values. When conflicts are detected, the application fails to start.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we point out that it is Route and RouteAlias combined with any RoutePrefix?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this mention that also client side paths are evaluated with the server side routes?



[discussion-id]`693776E5-D147-403A-A01D-04A3E9BF46AC`
Loading