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

Conversation

tepi
Copy link
Contributor

@tepi tepi commented Jan 15, 2025

Fixes #3969

@github-actions github-actions bot added the Language unchecked English language and AsciiDoc formatting checks haven't been done label Jan 15, 2025
@russelljtdyer russelljtdyer added Language checking English language and AsciiDoc formatting checking is in progress and removed Language unchecked English language and AsciiDoc formatting checks haven't been done labels Jan 15, 2025
@russelljtdyer russelljtdyer added Language checked English language and AsciiDoc formatting checks done and removed Language checking English language and AsciiDoc formatting checking is in progress labels Jan 15, 2025
@mshabarov mshabarov requested a review from caalador January 20, 2025 12:43
@@ -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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Language checked English language and AsciiDoc formatting checks done
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Routing docs should explicitly warn about duplicate routes
3 participants