Skip to content
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

Shared and Stage Specific Object Bag #20

Open
malicean opened this issue Mar 4, 2021 · 1 comment
Open

Shared and Stage Specific Object Bag #20

malicean opened this issue Mar 4, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@malicean
Copy link
Contributor

malicean commented Mar 4, 2021

There should be an object collection with Import<T>() and Export<T>(T value) methods, similar to the old kernel system but greatly simplified. There should be one specific to each individual stage, and there should be one that is shared amongst all stages (like how asset loaders are now). This would remove the static requirements from inter-plugin APIs.

@malicean
Copy link
Contributor Author

Furthermore, object collections should be scoped to mods. Doing otherwise could cause type conflicts between mods, and a conflict is the last thing that a mod-interop feature should allow for. With this in mind, plugins of the mod should get a mutable object bag (has Export<T>(T value)), but everyone else should only get an immutable object bag (does not have Export<T>(T value).

@malicean malicean self-assigned this Mar 25, 2021
@malicean malicean removed their assignment Mar 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant