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.

Sign up for GitHub

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

Jump to bottom

Split classes into APIs and implementations #201

Closed
haykam821 opened this issue Jan 8, 2022 · 1 comment
Closed

Split classes into APIs and implementations #201

haykam821 opened this issue Jan 8, 2022 · 1 comment
Labels
breaking change
Milestone
0.6.0

Comments

@haykam821
Copy link
Contributor

Fabric API follows an API/implementation model, where each module is split into three packages:

  • api package - Contains interfaces and utility classes that API consumers reference directly
  • impl package - Contains implementations of the API that are references by helper methods in the API
  • mixin package - Contains mixins necessary to make functionality work

Plasmid, and in particular its core game API, should more closely follow this API structure. Currently, some APIs use interfaces, but aren't placed in separate packages.
@Patbox Patbox added this to the 0.6.0 milestone Apr 13, 2022
@haykam821
Copy link
Contributor Author

Package separation was implemented in 61ae525.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
breaking change
Projects
None yet
Milestone
0.6.0
Development

No branches or pull requests
2 participants
@haykam821 @Patbox