NativeScript / NativeScript/angular

Bug: Named Outlet non responsive after `clearHistory` navigation

未关闭
#39 7 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

主要语言
TypeScript
星标
55
派生
13
平均合并
16 分钟
30 天内合并 PR
1

描述

Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):

  • CLI: 8.1.3
  • Cross-platform modules: NA
  • Android Runtime: 8.1.1
  • iOS Runtime: Not Tested
  • Plugin(s): @nativescript-community/ui-material-bottomnavigationbar
  • NativeScript-Angular: 12.2.0
  • Angular: 12.2.0

Describe the bug
When navigating to a nested route (one with a named outlet) after a clearHistory a navigation event would fire, but the outlet would not be updated

To Reproduce
Clone https://github.com/herefishyfish/named-router-navigation-bug
Start Android application
Press "Go to dashboard"
Press "Nested route in navbar"
Press Notifications tab
Press Todos tab
Press "Nested route in navbar"

Expected behavior
For the second press of Nested route in navbar to navigate to the nested route.

Sample project
https://github.com/herefishyfish/named-router-navigation-bug

Additional context
There was a few messages in Discord about this:
https://discord.com/channels/603595811204366337/606457628729671691/895530953068408894

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

克隆链接的 named-router-navigation-bug sample 并在 Android 上运行。按照列出的导航序列操作,然后跟踪 clearHistory 所涉及的 NativeScript Angular 路由和 named-outlet 处理。完成标准是第二次按下“Nested route in navbar”后嵌套路由得到更新,并且相关导航行为由回归检查覆盖。

由索引模型根据 Issue 内容生成。

评估

技术栈
angular, typescript
领域
mobile
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
基本清楚
新手友好度
35/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。