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: use Storage interface instead of direct struct #113

Merged
merged 1 commit into from
Jan 28, 2024

Conversation

yitsushi
Copy link
Owner

It can get quiet hard to test structs in Go and functions using them. With this, the rest of the code can be mocked easier with a TestBackend which is just sits in memory and no encryption. The encryption should be tested on storage layer, but the rest of the application should care only about the exposed functions.

related to #8 and #37

References:

It can get quiet hard to test structs in Go and functions using them.
With this, the rest of the code can be mocked easier with a TestBackend
which is just sits in memory and no encryption. The encryption should be
tested on storage layer, but the rest of the application should care
only about the exposed functions.

related to #8 and #37

References:
- #8
- #37

Signed-off-by: Victoria Nadasdi <victoria@efertone.me>
@yitsushi yitsushi merged commit 0253264 into main Jan 28, 2024
8 checks passed
@yitsushi yitsushi deleted the refactor-storage branch January 28, 2024 16:16
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 this pull request may close these issues.

None yet

1 participant