Fix NamedEvent resolution for route aliasing #483
Merged
Conversation
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
jlabedo
force-pushed
the
fix-named-event-parsing
branch
from
c01c531 to
4662b60
Compare
jlabedo
changed the title
unixslayer
approved these changes
Jun 8, 2025
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.
Why is this change proposed?
Fix
NamedEventresolution for routing aliasing to avoid BCDescription of Changes
Routing aliasing introduced in #479 requires
NamedEventclasses to be added to resolved classes to parse attributes. This was not required before becauseNamedEventattribute was resolved at runtime.Pull Request Contribution Terms