Enforce composable target diagnostics for menu applier boundaries#2777
Merged
Ivan Matkov (MatkovIvan) merged 4 commits intoFeb 18, 2026
Conversation
Oleksandr Karpovich (eymar)
approved these changes
Feb 18, 2026
Pavel Shishkin (shishkin-pavel)
approved these changes
Feb 18, 2026
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.
CMP-7106 Use separate
ComposableTargetMarkerfor desktop menu APIInvalid API mixing such as putting UI composables into menu DSL (or vice versa) can fail at runtime due to applier mismatch. This change improves compile-time detection and reduces runtime-only failures.
MenuComposableMenuComposablewhere menu applier is expected@ComposableOpenTarget(-1).JMenuBarapplier (SwingApplier-based path)Testing
Now produces
Release Notes
Features - Desktop