-
Notifications
You must be signed in to change notification settings - Fork 11
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
Descriptor extensions #65
Comments
Descriptor extensions can be used for configuration. e.g. AttrConfig. To support this well, inheritance should have a merging strategy that enables each component to be inherited individually. For merging the descriptor portion, the set of descriptor fields is defined as all fields that aren't The To block inheritance, RootDesc.config
The config constructor returns a RootDesc with only the config fields specified by config. |
Handle desc extensions separately from desc format by implementing a generic json patching system. Types:
Formats:
Libraries:
Certain fields of Desc.Extensions are interpreted in certain ways: rbxmk.globalDesc.Extensions = {
Elements = ..., -- Extends elements in Desc.
Config = ..., -- Additional non-element-specific config.
Behaviors = ..., -- Instance behaviors.
} Flags:
|
$rbxmkExtensions
field in the descriptor root, for forward-compatibility with Roblox's API dump format.$rbxmkConfig
field in the descriptor root.Example descriptor file:
Example patch that enhances a property with a default value:
Example patch that modifies global BrickColor data:
The text was updated successfully, but these errors were encountered: