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

[FEATURE] Dedicated crates for wadm types, wadm API #250

Closed
protochron opened this issue Apr 2, 2024 · 0 comments · Fixed by #287
Closed

[FEATURE] Dedicated crates for wadm types, wadm API #250

protochron opened this issue Apr 2, 2024 · 0 comments · Fixed by #287

Comments

@protochron
Copy link
Contributor

After chatting with @brooksmtownsend, we realized it might be useful to have dedicated crates for the Wadm API and for the various event and model types that we use. While they're all public types and can be consumed by other software, having them exposed as separate crates would allow downstream consumers to not have to depend on the entire wadm codebase in order to make an API call or parse a manifest. It could also be nice for introducing new features or changes using cargo feature flags and generally just decouple the data that wadm exposes from the underlying scheduler codebase

@protochron protochron changed the title [FEATURE]: dedicated crates for wadm types, wadm API [FEATURE] Dedicated crates for wadm types, wadm API Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant