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.

Sign up for GitHub

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

Jump to bottom

fix: fix interface name in navigation docs (CP: latest) #3319

Merged
merged 2 commits into from
Apr 8, 2024
Merged

fix: fix interface name in navigation docs (CP: latest) #3319

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d038ff6
fix: fix interface name in navigation docs (CP: latest)
mcollovati Apr 3, 2024
3da6180
Merge branch 'latest' into fix/hasurlparameter_interface_name_latest
mshabarov Apr 8, 2024
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
2 changes: 1 addition & 1 deletion articles/routing/navigation.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ If deep linking is required, the target view must <<updating-url-parameters#,mai

=== Passing Data Using Route Parameters

If your target view implements [interfacename]`HasRouteParameters`, you can submit trivial data to the target view as route parameters.
If your target view implements [interfacename]`HasUrlParameter`, you can submit trivial data to the target view as route parameters.
Compared to directly interacting with the target views Java API, this method automatically maintains the URL, which is beneficial for deep linking.
However, you can't pass more complex objects as route parameters as such, and you always need to consider data safety parameters that end up in URLs.

Expand Down
Loading