Optional example: portable inverse-patch regression fixtures

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

维护者通常 4 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
javascript
领域
testing

调研方向

The proposal links an external adapter and replay example at interaction-check/adapters/javascript/README.md and describes 12 passing steps for Immer 11.2.9. Read that example and the native Immer tests to understand the scenarios and how native tests serve as the reference. The proposal asks for feedback on sharing small reproducers, so first determine whether the project wants this example; no project files or acceptance criteria are named.

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

描述

Proposal

I built an external adapter and replay example for small, shareable regression traces. Three scenarios exercise immer 11.2.9 produceWithPatches/applyPatches: array removal/inverse replay, Unicode values, no-op identity and structural sharing. All 12 steps pass.

Motivation

A fixed sequence and expected state can make a patch bug report easier to reproduce without writing a new harness. Native tests remain the reference.

Can this be solved in user-land code?

Yes. The adapter retains one patch pair; it is not an undo-stack or patch-rebasing implementation. I maintain the experimental interaction-check runner. The example uses pinned stable packages, stays outside the project and adds no runtime dependency. Feedback on whether this helps share small reproducers is welcome. This is not a request for a new Immer API.

主要语言
JavaScript
星标
29k
派生
905
平均合并
3 天 16 小时
30 天内合并 PR
22

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

immerjs/immer 的其他 Issue

查看 immerjs/immer 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

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