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

Separate API and UI models #20

Closed
Drumber opened this issue Oct 1, 2023 · 1 comment
Closed

Separate API and UI models #20

Drumber opened this issue Oct 1, 2023 · 1 comment

Comments

@Drumber
Copy link
Owner

Drumber commented Oct 1, 2023

Do not use the same model classes for the UI and Kitsu API. The API classes should not depend on any unnecessary classes, interfaces or annotations since these dependencies may change and introduce new side-effects (see issue #19).
@Drumber
Copy link
Owner Author

Drumber commented Jul 8, 2024

Improved in the major refactoring (see dev branch). Network (API), local (database) and presentation models are now strictly separated.

@Drumber Drumber closed this as completed Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
Kitsune Development
Status: Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Drumber