Skip to content

WIP: Permission Claims - Group Management [skip-ci] #1389

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

Draft
wants to merge 1 commit into
base: release-candidate
Choose a base branch
from

Conversation

rackstar
Copy link
Contributor

@rackstar rackstar commented May 19, 2025

Description

Closes #1386

Describe the changes made in this PR. A link to the issue is enough if it contains all the relevant information.

Testing

Explain how you tested your changes to ensure they work as expected.

Checklist

  • Performed a self-review of my own code
  • Made corresponding changes to the documentation

@rackstar rackstar marked this pull request as draft May 19, 2025 08:33
@rackstar rackstar changed the title WIP: Permission Claims - Group Management WIP: Permission Claims - Group Management [skip-ci] May 19, 2025
@rackstar
Copy link
Contributor Author

Discussion over slack, putting it here for visibility:

  1. should we make groupsCount / groupId to uint32 so its consistent and we don't have to convert?
assessingGroupId: groupId.toUint32()
  1. should we change the ipfsMetadata to bytes32?
string calldata ipfsMetadata
  1. on add/remove functions, should we add validation for groupId param (> 0 && <= groupsCount)?
  2. should we add validation against zero address assessor?
  3. should we add events to makeNewGroup and setGroupMetadata?


mapping(address assessor => EnumerableSet.UintSet) private _groupsForAssessor;

mapping(uint productTypeId => AssessmentData) private _assessmentData;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this be here or in the ProductType struct to ensure each product type always has an AssessmentData?

@duxxud duxxud force-pushed the feat/permissioned-assessment branch from ac47ecf to 07eaec7 Compare May 21, 2025 07:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Claim Assessment - assessment groups management
3 participants