Introduce display registry object 0xd & snapshots#23922
Merged
manolisliolios merged 6 commits intomainfrom Oct 15, 2025
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
mystenmark
approved these changes
Oct 14, 2025
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
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.
Description
Introduce all the logic (but not enable) for the creation of Display Registry (
0xd).This will land before #23710. On that PR, the feature flag will be enabled & will have e2e tests.
Test plan
Just testing that the existing tests pass.
This PR does not do the creation of the object, only sets up the types & logic so we can release in two steps (to avoid breaking indexing). Tests for that will be introduced in the PR that enables the feature flag, because the move code is not yet landed (so creation cannot really happen yet!)
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.