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 the data model storage format from the API that is supposed to be used #8914

Open
sschuberth opened this issue Jul 19, 2024 · 0 comments
Open

Separate the data model storage format from the API that is supposed to be used #8914

sschuberth opened this issue Jul 19, 2024 · 0 comments
Labels
enhancement Issues that are considered to be enhancements epic A "parent" issue that refers to multiple other issues model About the data model

Comments

@sschuberth
Copy link
Member

sschuberth commented Jul 19, 2024 •
edited
Loading

We should have an API for all of our model classes that is separate from the data classes used for serialization / file storage. That would allow for drop-in replacements of places to store data (like using a database for ORT results instead of files) and separate API refactoring from eventually breaking the storage format.

Related issues / discussions are:
@sschuberth sschuberth added enhancement Issues that are considered to be enhancements model About the data model epic A "parent" issue that refers to multiple other issues labels Jul 19, 2024
@sschuberth sschuberth mentioned this issue Jul 19, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Issues that are considered to be enhancements epic A "parent" issue that refers to multiple other issues model About the data model
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sschuberth