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

refactor: Hide database implementation behind an interface. #413

Merged
merged 1 commit into from
Jan 10, 2025

Conversation

iphydf
Copy link
Member

@iphydf iphydf commented Jan 9, 2025

Here, an interface makes sense, since it's an I/O class. Hiding its implementation makes it so changes to that implementation don't need a rebuild of all its (50+) client code files.


This change is Reviewable

@iphydf iphydf added this to the v1.18.2 milestone Jan 9, 2025
@github-actions github-actions bot added the refactor Refactoring production code, eg. renaming a variable, not affecting semantics label Jan 9, 2025
@iphydf iphydf marked this pull request as ready for review January 9, 2025 11:08
@iphydf iphydf force-pushed the db-interface branch 2 times, most recently from 649b226 to 4d62830 Compare January 9, 2025 11:30
Here, an interface makes sense, since it's an I/O class. Hiding its
implementation makes it so changes to that implementation don't need a
rebuild of all its (50+) client code files.
@toktok-releaser toktok-releaser merged commit e679e32 into TokTok:master Jan 10, 2025
31 checks passed
@iphydf iphydf deleted the db-interface branch January 10, 2025 22:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactor Refactoring production code, eg. renaming a variable, not affecting semantics
Development

Successfully merging this pull request may close these issues.

3 participants