The current verbiage for the ChildAccount contract and defined resources isn't great and can be improved from a descriptive as well as product perspective. This will also involve updating the contract, resources and Capabilities named in transactions & scripts.
Suggest A Solution
Below is the suggested new terminology from current to final state. If you have other suggestions, please comment in this issue.
Also note that we'll likely change ChildAccountInfo from a struct implementation to a struct interface, allowing others to define metadata more specific to their use case.
sisyphusSmiling
commented
1 year ago
Issue To Be Solved
The current verbiage for the
ChildAccountcontract and defined resources isn't great and can be improved from a descriptive as well as product perspective. This will also involve updating the contract, resources and Capabilities named in transactions & scripts.Suggest A Solution
Below is the suggested new terminology from current to final state. If you have other suggestions, please comment in this issue.
ChildAccount->LinkedAccountsChildAccountManager->LinkedAccountAdministratorChildAccountController->LinkedAccountOwnerChildAccountTag->LinkedAccountHandlerChildAccountInfo->LinkedAccountInfoAlso note that we'll likely change
ChildAccountInfofrom astructimplementation to astruct interface, allowing others to define metadata more specific to their use case.