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

Migrate missing features and fixes from old SDK

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
graphql, javascript, node.js
领域
api, backend

调研方向

检查 src/coffee/sync/product-sync.coffee 和 src/coffee/services/base.coffee 中对旧 SDK 的引用,以及链接的 PR 590。将 fork 后的 issues、PRs 和 commits 与新 SDK 进行比较,然后将缺失的修复和功能记录为迁移 TODO 列表;完成标准是提供一份经过审查且可执行的列表,涵盖 issue 中的示例。

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

描述

Type: Discussion

Topic for discussion

It is pity that we hit same issues with new SDK which has been addressed in old SDK already as for existing customers migration might be a costly enterprise as they might hit issues that were not present with old SDK. The reason is obviously that rewrite of new SDK was based on old SDK and as it took around 1 year of development all the fixes/features applied to old SDK during that time were not migrated to the new SDK release.

Suggestion

Review all issues/PRs/commits from old SDK implemented after rewrite fork and create a list of TODOs for migration like examples below.

Missing fixes/features

  • - Sync actions should first remove variants
  • - fetch all convenience function for multi-paged results
  • - GraphQL convenience method which allows to do GraphQL requests with single line instead of boiler plate utils in every project
  • - Provide GraphQL process function for paginated results and fetch all if one needs to load all paginated results into memory.
主要语言
JavaScript
星标
77
派生
70
PR 合并指标
30 天内没有已合并 PR

环境准备

从这里开始

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

commercetools/nodejs 的其他 Issue

查看 commercetools/nodejs 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

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