Shorten FQCNs in place inside compound type strings - #4112
Open
lacatoire wants to merge 5 commits into
Open
lacatoire wants to merge 5 commits into
lacatoire wants to merge 5 commits into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
lacatoire
force-pushed
the
fix/array-shape-truncation
branch
from
f4a00f8 to
5bab1c9
Compare
April 17, 2026 11:50
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
1 participant
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.
When a parameter type is a compound expression (e.g. array{name?: string, chartColor?: \\App\\ChartColor, scheme?: string}), the class:short presentation used to explode('\\\\') and keep only the last segment, dropping everything before the FQCN.
Now FQCNs are shortened in place via a callback, leaving the surrounding shape intact. Pure FQCN titles keep their existing behavior.
Fixes #4059.