Conversation
Contributor
There was a problem hiding this comment.
Hey - 我在这里留下了一些高层次的反馈:
- 在
buildItemCases中,nodePrefix参数现在传入的是LocationId,而不是原先的节点前缀,因此重命名该参数(以及任何相关变量)以反映它不再是节点前缀,会更加清晰且不易出错。 - 你在
SETTLEMENT_MAP的一些条目中添加了TextExpected,并且也在LOCATIONS中输出了TextExpected,但这里没有展示从SETTLEMENT_MAP/SETTLEMENTS映射到LOCATIONS的过程;值得确认的是,在新的前哨站配置中,TextExpected是否确实被传播到了loc中,而不是依然为undefined。
面向 AI 代理的提示
Please address the comments from this code review:
## Overall Comments
- In `buildItemCases`, the `nodePrefix` argument is now being passed `LocationId` instead of the original node prefix, so it would be clearer and less error-prone to rename the parameter (and any related variables) to reflect that it is no longer a node prefix.
- You added `TextExpected` to some entries in `SETTLEMENT_MAP` and also emit `TextExpected` from `LOCATIONS`, but the mapping from `SETTLEMENT_MAP`/`SETTLEMENTS` into `LOCATIONS` isn’t shown here; it’s worth verifying that `TextExpected` is actually propagated into `loc` and not left as `undefined` for the new outpost configurations.帮我变得更有用!请在每条评论上点 👍 或 👎,我会根据你的反馈改进后续的评审。
Original comment in English
Hey - I've left some high level feedback:
- In
buildItemCases, thenodePrefixargument is now being passedLocationIdinstead of the original node prefix, so it would be clearer and less error-prone to rename the parameter (and any related variables) to reflect that it is no longer a node prefix. - You added
TextExpectedto some entries inSETTLEMENT_MAPand also emitTextExpectedfromLOCATIONS, but the mapping fromSETTLEMENT_MAP/SETTLEMENTSintoLOCATIONSisn’t shown here; it’s worth verifying thatTextExpectedis actually propagated intolocand not left asundefinedfor the new outpost configurations.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- In `buildItemCases`, the `nodePrefix` argument is now being passed `LocationId` instead of the original node prefix, so it would be clearer and less error-prone to rename the parameter (and any related variables) to reflect that it is no longer a node prefix.
- You added `TextExpected` to some entries in `SETTLEMENT_MAP` and also emit `TextExpected` from `LOCATIONS`, but the mapping from `SETTLEMENT_MAP`/`SETTLEMENTS` into `LOCATIONS` isn’t shown here; it’s worth verifying that `TextExpected` is actually propagated into `loc` and not left as `undefined` for the new outpost configurations.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
Contributor
There was a problem hiding this comment.
Pull request overview
该 PR 旨在修复 SellProduct 在“优先售卖”场景下不生效的问题(OCR 结果带有 |、] 等 UI 前缀导致匹配失败),并同步重构 SellProduct 流水线产物的组织方式,提升据点识别与配置可维护性。
Changes:
- 为“优先物品选择”OCR 节点增加字符清洗(
replace),并在换货流程中加入“优先货品未识别到”的锚点处理与提示节点。 - 重构 SellProduct 流水线输出:按据点拆分为
Outposts/*.json,新增整合入口Sell.json,并补充生成器配置(task/pipeline 分离)。 - 调整任务模板与生成数据结构:以
LocationId统一节点前缀,并在生成时将“售卖尝试节点”的锚点与物品 case 对齐。
Reviewed changes
Copilot reviewed 14 out of 14 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| tools/pipeline-generate/SellProduct/task-template.jsonc | 任务模板改用 LocationId 对应流水线节点开关 |
| tools/pipeline-generate/SellProduct/task-config.json | 指向新的 task 模板文件名 |
| tools/pipeline-generate/SellProduct/README.md | 更新生成命令示例(task/pipeline 两套 config) |
| tools/pipeline-generate/SellProduct/pipeline-template.jsonc | 新增按据点生成的流水线模板(含 replace、锚点结构) |
| tools/pipeline-generate/SellProduct/pipeline-config.json | 新增 pipeline 生成配置,输出到 Outposts 目录 |
| tools/pipeline-generate/SellProduct/data.mjs | 扩展据点元数据与 item cases 生成逻辑(含优先缺失处理锚点) |
| assets/tasks/SellProduct.json | 任务中为 SellAttempt 节点补充锚点覆盖,配合优先缺失处理 |
| assets/resource/pipeline/SellProduct/ValleyIV.json | 删除旧的“整区合并”流水线文件 |
| assets/resource/pipeline/SellProduct/Sell.json | 新增整合入口(地区售卖入口节点) |
| assets/resource/pipeline/SellProduct/Outposts/*.json | 新增/更新按据点拆分的流水线节点定义 |
| assets/resource/pipeline/SellProduct/ChangeGoods.json | 增加优先货品 miss handler 的锚点分支与提示节点 |
a4cebbf to
461a75c
Compare
b30d332 to
55e35a3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fixed #1806
Sourcery 摘要
更新 SellProduct 流水线和位置信息元数据,以改进前哨站位置识别并修复优先出售行为。
Bug 修复:
功能增强:
文档:
Original summary in English
Summary by Sourcery
优化 SellProduct 流水线和元数据,更好地识别前哨据点位置,并确保在苔原和五菱定居点之间的优先售卖行为表现正确。
Bug 修复:
功能改进:
文档:
Original summary in English
Summary by Sourcery
Refine SellProduct pipelines and metadata to better recognize outpost locations and ensure priority selling behaves correctly across tundra and Wuling settlements.
Bug Fixes:
Enhancements:
Documentation: