Repository navigation
Introduce ComponentStore - #2457
Merged
Merged
Conversation
danirabbit
approved these changes
Nov 17, 2026
This is basically a code shuffle. It moves the component map and the component listmodel to a separate class `ComponentStore`. This is motivated by two things: - Reduce the scope of the FlatpakBackend. I want to move it more towards only handling jobs etc. and less managing packages. - Things like getting packages for an author etc. can be optimized with the components. Stuff like this doesn't require anything from flatpakbackend so IMO it makes more sense and would be a lot cleaner to have it in a separate class.
leolost2605
force-pushed
the
leolost/introduce-component-store
branch
from
November 17, 2026 07:10
e49ec93 to
4718b52
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is basically a code shuffle. It moves the component map and the component listmodel to a separate class
ComponentStore. This is motivated by two things: