You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the AccountComponentMetadata contains the following fields:
pubstructAccountComponentMetadata{/// The human-readable name of the component.name:String,/// A brief description of what this component is and how it works.description:String,/// The semantic version of the component./// This can be used to track and manage component upgrades.version:Version,/// A set of supported target account types for this component.targets:BTreeSet<AccountType>,/// A list of storage entries defining the component's storage layout and initialization/// values.storage:Vec<StorageEntry>,}
This struct can be serialized to and deserialized from TOML files.
There are some things that we could add to make this more useful, specially in the context of other systems "outside" of the protocol itself, like component registries.
As suggested during the PR review, some of these could build toward something like what the Rust ecosystem does (one can think of links to documentation, authors, categories, etc.)
The text was updated successfully, but these errors were encountered:
Currently, the
AccountComponentMetadata
contains the following fields:This struct can be serialized to and deserialized from TOML files.
There are some things that we could add to make this more useful, specially in the context of other systems "outside" of the protocol itself, like component registries.
As suggested during the PR review, some of these could build toward something like what the Rust ecosystem does (one can think of links to documentation, authors, categories, etc.)
The text was updated successfully, but these errors were encountered: