Refactoring persistence layer #1120
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ricardozanini
approved these changes
Jan 26, 2026
fjtirado
force-pushed
the
refactoring_persistence
branch
from
13e52c1 to
9df126c
Compare
Signed-off-by: fjtirado <ftirados@redhat.com>
fjtirado
force-pushed
the
refactoring_persistence
branch
from
9df126c to
2b6c5c9
Compare
fjtirado
force-pushed
the
refactoring_persistence
branch
3 times, most recently
from
e63221f to
b56be11
Compare
Signed-off-by: fjtirado <ftirados@redhat.com>
fjtirado
force-pushed
the
refactoring_persistence
branch
from
b56be11 to
a284de5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Refactoring persistence layer to make it easier development of pluging which persistence is not map based