Definitions: refactor JSON to struct mapping (backport #15621)#15623
Closed
mergify[bot] wants to merge 1 commit intov4.2.xfrom
Closed
Definitions: refactor JSON to struct mapping (backport #15621)#15623mergify[bot] wants to merge 1 commit intov4.2.xfrom
mergify[bot] wants to merge 1 commit intov4.2.xfrom
Conversation
to produce fewer atoms. Note that all the top-level definition keys are "known" atoms in the sense that they are definitely used/referenced during node boot before on-boot definition import even has a chance to run. (cherry picked from commit c25c92a)
Collaborator
|
Will merge manually, GitHub is having a rough day. |
the-mikedavis
pushed a commit
to amazon-mq/upstream-to-rabbitmq-server
that referenced
this pull request
Mar 4, 2026
…15621 Definitions: refactor JSON to struct mapping (backport rabbitmq#15621)
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.
Note that all the top-level definition keys
are "known" atoms in the sense that they are
definitely used/referenced during node boot before on-boot definition import even has a chance to run.
This is an automatic backport of pull request #15621 done by [Mergify](https://mergify.com).