From: Dominik Csapak <d.csapak@proxmox.com>
To: yew-devel@lists.proxmox.com
Subject: [yew-devel] [PATCH yew-widget-toolkit 1/2] state: navigation: add 'replace_relative_route' to NavigationContextExt
Date: Tue, 16 Dec 2025 10:55:18 +0100 [thread overview]
Message-ID: <20251216095529.1019541-1-d.csapak@proxmox.com> (raw)
so we can not only push new relative routes, but also replace the
current one.
To not duplicate that much code, refactor the absolute path generation
out, this even avoids some duplication we already had.
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
src/state/navigation_container.rs | 55 ++++++++++++++++---------------
1 file changed, 28 insertions(+), 27 deletions(-)
diff --git a/src/state/navigation_container.rs b/src/state/navigation_container.rs
index eced509..b9090eb 100644
--- a/src/state/navigation_container.rs
+++ b/src/state/navigation_container.rs
@@ -243,10 +243,25 @@ pub trait NavigationContextExt {
fn nav_context(&self) -> Option<NavigationContext>;
/// Returns the full route to this context ("/parent_path/path").
fn full_path(&self) -> Option<String>;
- /// Change the current route to "/parent_path/path".
+ /// Push a new route "/parent_path/path".
///
/// Only works if the scope provides a [Navigator](yew_router::navigator::Navigator).
fn push_relative_route(&self, path: &str);
+ /// Replace the current route with "/parent_path/path".
+ ///
+ /// Only works if the scope provides a [Navigator](yew_router::navigator::Navigator).
+ fn replace_relative_route(&self, path: &str);
+}
+
+fn get_new_absolute_path<COMP: Component>(scope: &yew::html::Scope<COMP>, path: &str) -> String {
+ let path = normalize_segment(path);
+ let parent_path = scope
+ .context::<NavigationContext>(Callback::from(|_| {}))
+ .and_then(|(ctx, _)| ctx.parent_path);
+ match parent_path {
+ Some(parent_path) => format!("{}/{}", parent_path, path),
+ None => format!("/{}", path),
+ }
}
impl<COMP: Component> NavigationContextExt for yew::html::Scope<COMP> {
@@ -260,32 +275,18 @@ impl<COMP: Component> NavigationContextExt for yew::html::Scope<COMP> {
}
fn push_relative_route(&self, path: &str) {
- let path = normalize_segment(path);
- //log::info!("PUSH REL {}", path);
- if let Some((nav_ctx, _handle)) = self.context::<NavigationContext>(Callback::from(|_| {}))
- {
- let abs_path = match &nav_ctx.parent_path {
- Some(parent_path) => format!("{}/{}", parent_path, path),
- None => format!("/{}", path),
- };
- match self.navigator() {
- Some(navigator) => {
- navigator.push(&AnyRoute::new(abs_path));
- }
- None => {
- log::error!("no Navigator found");
- }
- }
- } else {
- match self.navigator() {
- Some(navigator) => {
- let path = format!("/{}", path);
- navigator.push(&AnyRoute::new(path));
- }
- None => {
- log::error!("no Navigator found");
- }
- }
+ let new_path = get_new_absolute_path(self, path);
+ match self.navigator() {
+ Some(navigator) => navigator.push(&AnyRoute::new(new_path)),
+ None => log::error!("no Navigator found"),
+ }
+ }
+
+ fn replace_relative_route(&self, path: &str) {
+ let new_path = get_new_absolute_path(self, path);
+ match self.navigator() {
+ Some(navigator) => navigator.replace(&AnyRoute::new(new_path)),
+ None => log::error!("no Navigator found"),
}
}
}
--
2.47.3
_______________________________________________
yew-devel mailing list
yew-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/yew-devel
next reply other threads:[~2025-12-16 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 9:55 Dominik Csapak [this message]
2025-12-16 9:55 ` [yew-devel] [PATCH yew-widget-toolkit 2/2] widget: tab panel: improve route handling on creation Dominik Csapak
2025-12-16 10:35 ` [yew-devel] applied: " Dietmar Maurer
2025-12-16 10:35 ` [yew-devel] applied: [PATCH yew-widget-toolkit 1/2] state: navigation: add 'replace_relative_route' to NavigationContextExt Dietmar Maurer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251216095529.1019541-1-d.csapak@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=yew-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox