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

ClientFilestore: make the dat folder optional #150

Merged
merged 1 commit into from
Mar 28, 2024

Conversation

sosthene-nitrokey
Copy link
Contributor

@sosthene-nitrokey sosthene-nitrokey commented Mar 4, 2024

This allows custom backends to improve their storage, reducing the number of required intermediary directories.

Copy link
Member

@robin-nitrokey robin-nitrokey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe it would make sense to also have this distinction in the type system in the long term, e. g. use a RawClientFilestore type, or ScopedFilestore<Client>, ScopedFilestore<RawClient>, ...? I fear that the current implementation could lead to subtle bugs when the wrong constructor is used.

@sosthene-nitrokey
Copy link
Contributor Author

In the future yes. But not until we remove the configuration from the trussed-auth and se050 backends. Otherwise we can't just change the constructor based on the config.

@sosthene-nitrokey sosthene-nitrokey merged commit 2d0e667 into trussed-dev:main Mar 28, 2024
2 checks passed
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.

2 participants