You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Fix #1773] Optionally publish on legacy CE type - #1814
The reason will be displayed to describe this comment to others. Learn more.
🟡 Changes recommended
Method-call initializers make all fourteen public lifecycle type fields non-constant, breaking compilation for consumers that use them as switch labels or annotation values.
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
The event-type helper omits V7 types, preventing listeners registered through it from receiving legacy events, and the V7-only and dual-publication paths lack regression coverage.
EventType.toString() always uses V8, so this helper omits every legacy type even when V7 publication is enabled. Consumers registering listeners through this list, as LifeCycleEventsTest.init() does, will never receive the legacy events; with V7-only configuration they receive no lifecycle events at all. Include both supported prefixes here, or add an overload that enumerates the application's configured prefixes.
Add lifecycle test coverage for V7 and dual publication
The existing lifecycle tests exercise only the default V8 configuration, and no test calls withLifeCycleEventTypes. The new V7 and dual-publication paths therefore have no regression coverage. Extend LifeCycleEventsTest to cover V7-only and V7+V8 configurations, asserting the exact emitted types, event counts, and matching payloads, while retaining the default V8 assertion.
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
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.
Fix #1773