We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
You can continue the conversation there. Go to discussion →
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
This might be useful during
The text was updated successfully, but these errors were encountered:
Something similar is already cooking:
#24
Although, I understand the needs, it would throw even more responsibility into a layer that's technically just a thin generically coded wrapper.
Fridge is meant to be just stupid fetch and store mechanism.
The rest is "upper layer" logic.
With Identifiable in place, methods for IO will get another overloaded function to handle the struct.
Identifiable
struct
But, nice suggestions to think about.
Sorry, something went wrong.
Here's another issue created out of this, so that we can expand it if needed: #46
Yeah, agree! I totally understand, less complexity is better, so far I like it
But this part ☝️
development - want to clean up my mess..
Hmm 🤔 I understand this need quite well. Yup it can get messy over time.
Right now there is drop(..) method. Pass the id and the object (file) is physically erased.
drop(..)
Perhaps expanding it to dropAll ? 🤔
dropAll
No branches or pull requests
This might be useful during
The text was updated successfully, but these errors were encountered: