feat(licensing): enable multi-license attachment and licensing config during IP registration #134
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.
Description
This PR introduces support for multi-license attachment and the ability to set licensing configurations during IP registration. It also updates the periphery contracts to align with recent protocol core API changes. Furthermore, signature requirements in
LicenseAttachmentWorkflows
have been streamlined usingsetBatchPermissions
.Key Changes
PILTermsData
andLicenseData
inWorkflowStructs
to consolidate licensing-related parameters.LicenseAttachmentWorkflows
functions to support an array ofPILTermsData
for registering and attaching multiple PIL terms and licensing configurations to IPs.GroupingWorkflows
functions to accept an array ofLicenseData
for attaching multiple licenses (license template, license terms ID, and licensing config) to IPs.LicenseAttachmentWorkflows
, all functions now require at most one signature.Related Issue
Notes
This PR introduces new interface changes. Backward compatibility will be addressed in a future PR (#131).