Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Regional protection permissions [It is expected to support the direct deletion of regional protection permissions within the regional scope] #4165

Open
2 tasks done
18860852449 opened this issue Nov 27, 2024 · 1 comment
Assignees
Labels

Comments

@18860852449
Copy link

初始清单

  • 这真的是个问题吗?
  • 我已经在 Github Issues 中搜索过了,但没有找到类似的问题。

问题

场景:页面加载时后,整个sheet的单元格都进入禁止编辑状态,此时会调用后端 API 得到多组区域范围,然后期望可以调用 Facade API 来将这些区域范围的禁止编辑状态更改为可编辑状态。
问题:const permission = univerAPI.getPermission();permission.removeRangeProtection(unitId, subUnitId, ruleIds); 目前官方提供的这个 API 需要 ruleIds,而我的场景是不存在 ruleIds 的
期望:我期望可以直接根据多组区域范围 来删除区域保护权限

@univer-bot univer-bot bot changed the title [Feature] 区域保护权限[期望支持区域范围直接删除区域保护权限] [Feature] Regional protection permissions [It is expected to support the direct deletion of regional protection permissions within the regional scope] Nov 27, 2024
@univer-bot
Copy link

univer-bot bot commented Nov 27, 2024

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

Origin Title: [Feature] 区域保护权限[期望支持区域范围直接删除区域保护权限]

Title: [Feature] Regional protection permissions [It is expected to support the direct deletion of regional protection permissions within the regional scope]


Initial list

  • Is this really a problem?
  • I've searched Github Issues but haven't found any similar issues.

question

Scenario: After the page is loaded, the cells in the entire sheet enter the edit-prohibited state. At this time, the back-end API is called to obtain multiple sets of area ranges, and then the Facade API is expected to be called to change the edit-prohibited state of these area ranges to editable. state.
Problem: const permission = univerAPI.getPermission();permission.removeRangeProtection(unitId, subUnitId, ruleIds); The currently officially provided API requires ruleIds, but ruleIds does not exist in my scenario.
Expectation: I expect to be able to delete zone protection permissions directly based on multiple sets of zone ranges

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants