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

Current way of dealing with legacy interfaces is very messy #57

Open
MrApplejuice opened this issue Nov 17, 2023 · 0 comments
Open

Current way of dealing with legacy interfaces is very messy #57

MrApplejuice opened this issue Nov 17, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@MrApplejuice
Copy link
Collaborator

Old pumping entries had a different structure (time) and then new-style pumping structures (start and end). This required introducing a "compatibility layer". The current one is baked straight into the data structure which does not make a whole lot of sense. It makes the data structure with old and new styles. However, this way of dealing with API updates does not scale very well. In the future, we can expect more breaking changes and more needs to support at least two types of APIs so that users can get have some leeway to update their babybuddy server.

@MrApplejuice MrApplejuice added the enhancement New feature or request label Nov 17, 2023
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