Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Migrate the iOS new runtime off the data-binding APIs deprecated in rive-ios 6.28.0

已关闭
#403 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@mfazekas 已经在做这个了。

开始于 2026年10月14日。

  • #423 来自 @mfazekas —— 未关闭

评估

难度
4/5
预计耗时
3-5 天
新手友好度
68/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
react-native, swift
领域
mobile

调研方向

Start with ios/new/RiveReactNativeView.swift and the rive-ios 6.28.0 release notes; trace the current DataBind, viewModelInstance, bindViewModelInstance, and pendingBindInstance paths. Done means the deprecated APIs are no longer used, authored default instances and async rebinding still work for auto and by-name data binding, and the harness passes on both runtimes.

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

描述

enhancement iOS

rive-ios 6.28.0 (release notes) deprecates the concurrency data-binding API that ios/new/RiveReactNativeView.swift is built on. Everything still works on 6.28.0 (bumped in #401; the harness passes on both runtimes, warnings only), but these are slated for removal in a future release:

  • DataBind and Rive(file:artboard:stateMachine:dataBind:fit:) → pass explicitly bound components to Rive(file:artboard:stateMachine:)
  • StateMachine.bindViewModelInstance(_:) → try await stateMachine.bindViewModelInstances(main:globals:), which is async
  • Rive.viewModelInstance → create and retain the instance ourselves

Things the migration has to handle:

  1. dataBind auto and by-name must create the authored default instance explicitly, since getViewModelInstance() can no longer read it from Rive.
  2. Rebinding becomes async, which affects the dataBind-only change path and pendingBindInstance.
  3. Views now redraw automatically when bound instances change.

6.28.0 also adds global view models, font binding and blob binding, which we could expose once this is done.

主要语言
TypeScript
星标
157
派生
17
平均合并
1 天 10 小时
30 天内合并 PR
20

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

rive-app/rive-nitro-react-native 的其他 Issue

查看 rive-app/rive-nitro-react-native 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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