-
-
Notifications
You must be signed in to change notification settings - Fork 220
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
first persistence draft #866
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #866 +/- ##
==========================================
- Coverage 81.51% 81.31% -0.20%
==========================================
Files 160 165 +5
Lines 9033 9280 +247
==========================================
+ Hits 7363 7546 +183
- Misses 1418 1467 +49
- Partials 252 267 +15
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
// Map are used to store VARIABLE data | ||
// for transactions, this data structured is designed | ||
// to store slices of data for keys | ||
// Important: CollectionMaps ARE NOT concurrent safe | ||
type Map interface { | ||
Keyed | ||
Editable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not a breaking change, as it still implements Keyed and it keeps the same functions (?)
Adds persistence support using in-memory storage.
Current challenges
collections.Map
, now it implementscollection.Editable
, which is also implemented bycollection.Persistent
. That way, both persistent and map collections can be easily edited insetvar
. Maps are still the same, the only difference is that some methods come from editable.Usage