Repository navigation
Conversation
This was referenced Nov 6, 2026
Steveb-p
force-pushed
the
feature/language-bitmask-4-content-type-6.0
branch
from
November 6, 2026 18:54
b9a4423 to
f70bf8d
Compare
Steveb-p
force-pushed
the
feature/language-bitmask-4-content-type-6.0
branch
from
November 6, 2026 19:45
f70bf8d to
042b461
Compare
Steveb-p
force-pushed
the
feature/language-bitmask-4-content-type-6.0
branch
from
November 10, 2026 12:12
042b461 to
99dcb54
Compare
konradoboza
reviewed
Nov 12, 2026
Steveb-p
force-pushed
the
feature/language-bitmask-4-content-type-6.0
branch
2 times, most recently
from
November 15, 2026 18:49
5a88ce9 to
dc64490
Compare
konradoboza
approved these changes
Nov 16, 2026
alongosz
approved these changes
Nov 16, 2026
Steveb-p
force-pushed
the
feature/language-bitmask-4-content-type-6.0
branch
from
November 17, 2026 11:19
dc64490 to
161323d
Compare
Steveb-p
force-pushed
the
feature/language-bitmask-4-content-type-6.0
branch
2 times, most recently
from
November 18, 2026 12:13
9fb3864 to
838aeb5
Compare
Steveb-p
force-pushed
the
feature/language-bitmask-4-content-type-6.0
branch
from
November 18, 2026 13:06
838aeb5 to
e57e645
Compare
Steveb-p
force-pushed
the
feature/language-bitmask-4-content-type-6.0
branch
from
November 18, 2026 15:35
e57e645 to
49018f0
Compare
Content types read their languages from ibexa_content_type_name instead of decoding the type's language_mask, and resolve language ids through the language handler instead of MaskGenerator. They keep writing the mask and the always-available bit of their name rows until the bitmask is removed.
…pes in the content type mapper
Steveb-p
force-pushed
the
feature/language-bitmask-4-content-type-6.0
branch
from
November 21, 2026 16:16
49018f0 to
f6c3bae
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 4 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:
Content types read their languages from
ibexa_content_type_name(Type\Gateway::loadContentTypeTranslations()) instead of decodingibexa_content_type.language_mask, and resolve language ids through the language handler instead ofMaskGenerator. They still write the mask and the always-available bit of their name rows until #946.