Maintenance: Upgrade to React v16 · frintjs/frint#435

(4 评论) (0 反应) (0 负责人)JavaScript (746 star) (37 fork)batch import

help wantedproposal

描述

Currently

Our API of frint-react is based on the context API of React v15.

React v16 still supports the old (v15) context API in deprecated mode, but also makes room for additional improvements.

It has also introduced APIs like getDerivedStateFromProps , making way for better async rendering (while also deprecating componentWillReceiveProps).

Proposal

We already have some additional proposals which make the API of FrintJS more simpler and stays close to the Component lifecycle where possible. Making it even easier to migrate to React v16:

#424: Access to app instance synchronously
#428: Region component with render prop support
#433: MountApp component
#436: Pass Region's props to Child Apps' root Components directly

While migrating to React v16, we can:

Drop observe HoC
Drop data prop in Region component
Drop RegionService

Because parent props as a stream would be difficult to access, since componentWillReceiveProps is already deprecated and will be gone in React v17.

It will have to be a breaking change.

贡献者指南

技术栈: reactjavascript
领域: frontend
议题类型: refactor
难度: 3
预计时间: 1-2 days
活动状态: stale
清晰度: mostly clear
前置要求: React v15 API knowledgeUnderstanding of frint reactComponent lifecycleAsync rendering concepts
新手友好度: 25
研究方向: The issue requires upgrading frint react to React v16, which involves dropping the `observe` HoC, `data` prop in Region, and RegionService. It also references sub issues #424, #428, #433, #436. Contributors should first understand the current React v15 context API usage and then replace deprecated lifecycle methods like componentWillReceiveProps with getDerivedStateFromProps. It would be helpful to review the linked PRs that were already completed (e.g., #428, #436) to understand the new patterns. Since this is a breaking change, careful testing is needed.