check-config: groupProfiles order warning compares fields lists, not effective levels

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
78/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
javascript
领域
backend, cli

调研方向

Find the check-config logic that checks groupProfiles order and the related tests. Read how source policies are merged with profiles, then compare effective levels per source. Add the finance/staff example as a regression test; done means it no longer reports an order warning when both profiles effectively show the fields.

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

描述

area:server bug

check-config reports a false order warning for groupProfiles. It fires when a later profile lists only fields at a level that the earlier profile already gets from the source policy.

Example:

  • finance: {fields: {Sales: show, amount: show, Customer: show}}
  • staff: {fields: {Region: show, Product: show}}

check-config warns "entry 2 (staff) shows fields that entry 1 (finance) holds back". But the source policy already shows Region and Product, so the effective level is show for both profiles.

Not affected: runtime behaviour. The profile choice is correct; only the warning is wrong.

Fix: compare the effective levels per source (source policy merged with the profile), not the profiles' fields lists. Add the example as a test.

Found while setting up a live test stack with three test users.

主要语言
JavaScript
星标
1
派生
1
平均合并
3 小时 34 分钟
30 天内合并 PR
213

环境准备

从这里开始

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

eizedev/pivotkit 的其他 Issue

查看 eizedev/pivotkit 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

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