Implement PoC (proof of concept) of the State Management that increase performance
@korel-san 已经在做这个了。
开始于 2023年2月14日。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- typescript
- 领域
- frontend
调研方向
首先，根据所述的轻量、简单、routing-subscription 和会话存储标准，调查 elf、effector 和 ng-state。然后，在创建 src/state/actual-route-state.repository.ts 之前，检查现有的 routing-state 解析以及 StringHelpers.encodeObjToUrlString 的使用情况。完成的标准是：通过一个仅限本地使用的 repository 提供统一的 actual route state，并且 production 中不存在任何实例。
由索引模型根据 Issue 内容生成。
描述
The main goal of the task: create State Service that contains the parsed actual route state.
More details:
The routing state depends on the page and functionality of the page. Now many components trying to parse it, which increased code duplication and worked not properly in some cases. So, for the unification of the actual routing state, we consider separating functionality in service, which would handle the actual route state, and every component would be asked from its real data for their purposes.
We don't want to use current state management ngrx due to the high level of tied dependency of the current implementation, so not to add extra naming and have a more lightweight solution, we want to use another tool for this PoC will allow us to not affect the current performance.
Actual implementation plan:
- investigate 2-3 state management packages: elf, effector, ng-state
Points on which we need to focus
- it should be lightweight
- it should be pretty simple
- package should allow to manipulate of routing (subscription, session storage)
- create a state folder in the src and add there
actual-route-state.repository.ts. In this file, we need to create a repository that would manage the routing state. Please, take into account, that this state management should work only for the local environment. On prod env, this instance should not exist. - In some cases probably you will need to create Adapters that would convert the current routing state to a meaningful one. For example for pages where we have
protectedquery parameters via the encoding ofStringHelpers.encodeObjToUrlString. So after this implementation, every developer should be allowed to see the state of this service on every page of the project.
- 主要语言
- TypeScript
- 星标
- 12
- 派生
- 7
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
AbsaOSS/spline-ui 的其他 Issue
-
enhancement
难度 3/5 1-2 天 新手友好度 20/100
-
bug
难度 3/5 1-2 天 新手友好度 20/100
-
Update Angular & other dependencies可能已有人在做 @korel-san 于 675 天前认领。 未关闭dependencies
难度 4/5 3-5 天 新手友好度 10/100
-
bug
难度 3/5 1-2 天 新手友好度 35/100
-
bug
难度 3/5 1-2 天 新手友好度 45/100
查看 AbsaOSS/spline-ui 的全部 Issue
相似的 Issue
-
[analytics-core] getQueryParams does not decode `+` as space and truncates values containing `=`未关闭bug
难度 2/5 1-3 小时 新手友好度 82/100
amplitude/Amplitude-TypeScript#2179 · 1 条评论 ·
维护者通常 2 天内回复
-
ci good first issue severity: low
难度 2/5 1-3 小时 新手友好度 68/100
TMHSDigital/GH-Arcade#111 ·
-
AsnIntegerConverter.toASN coerces strings with +value, rounding integers outside safe-integer range未关闭
难度 2/5 1-3 小时 新手友好度 78/100
PeculiarVentures/asn1-schema#189 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 4 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100