Repository navigation
Conversation
This was referenced Nov 6, 2026
Steveb-p
force-pushed
the
feature/language-bitmask-5-object-states-6.0
branch
from
November 6, 2026 18:54
d4754ee to
9cc7361
Compare
Steveb-p
force-pushed
the
feature/language-bitmask-5-object-states-6.0
branch
from
November 6, 2026 19:45
9cc7361 to
7bb375d
Compare
Steveb-p
force-pushed
the
feature/language-bitmask-5-object-states-6.0
branch
from
November 10, 2026 12:12
7bb375d to
dacbea9
Compare
konradoboza
approved these changes
Nov 12, 2026
Steveb-p
force-pushed
the
feature/language-bitmask-5-object-states-6.0
branch
from
November 13, 2026 09:10
dacbea9 to
93c9471
Compare
alongosz
reviewed
Nov 14, 2026
Steveb-p
force-pushed
the
feature/language-bitmask-5-object-states-6.0
branch
from
November 15, 2026 18:49
93c9471 to
921daa2
Compare
Steveb-p
force-pushed
the
feature/language-bitmask-5-object-states-6.0
branch
from
November 17, 2026 11:19
921daa2 to
5ebe47a
Compare
Steveb-p
force-pushed
the
feature/language-bitmask-5-object-states-6.0
branch
from
November 18, 2026 11:50
5ebe47a to
dbb5f7d
Compare
Steveb-p
force-pushed
the
feature/language-bitmask-5-object-states-6.0
branch
from
November 18, 2026 12:13
dbb5f7d to
7376671
Compare
Steveb-p
force-pushed
the
feature/language-bitmask-5-object-states-6.0
branch
2 times, most recently
from
November 18, 2026 15:35
bd2f280 to
23e1749
Compare
alongosz
approved these changes
Nov 18, 2026
Object states resolve language ids through the language handler instead of MaskGenerator. They keep writing the masks and the always-available bit until the bitmask is removed.
Steveb-p
force-pushed
the
feature/language-bitmask-5-object-states-6.0
branch
from
November 21, 2026 16:16
23e1749 to
4849948
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.



Note
Part 5 of 6 of the language bitmask removal. Each part is green on its own; the bitmask keeps being written until #946 removes it.
Related PRs:
The stack that replaces the language bitmask, bottom to top. Each part is green and can be merged on its own, in this order:
MaskGeneratoribexa/installer#246 goes first, as the Experience content it provisions has to match each step, and ibexa/installer#250 drops its schema checks after #946. ibexa/data-intelligence-layer#63 goes with #946.
Description:
Object states and their groups resolve language ids through the language handler instead of
MaskGenerator, the last user of it besides the content gateway. Nothing reads their masks, but they keep writing them and the always-available bit until #946, so its migrations see the same data on every route.