Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support nested definitions in GetMessageClassesForFiles #20112

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

copybara-service[bot]
Copy link

@copybara-service copybara-service bot commented Jan 26, 2025

Support nested definitions in GetMessageClassesForFiles

Otherwise downstream callers must explicitly fetch and generate message classes for nested definitions. (For example here.)

Example:

message NestedTypeMessage {
  message NestedType {
      string data = 1;
    }

  NestedType nested = 1;
}

Currently GetMessageClassesForFiles() will only return NestedTypeMessage, but miss NestedTypeMessage.NestedType (and any arbitrary level of nested definitions).

This is an unexpected deviation from the comment that says that it will find and resolve all dependencies.

@copybara-service copybara-service bot changed the title Internal change Support nested definitions in GetMessageClassesForFiles Jan 26, 2025
Otherwise downstream callers must explicitly fetch and generate message classes for nested definitions. (For example [here](foxglove/mcap#1321).)

Example:
```
message NestedTypeMessage {
  message NestedType {
      string data = 1;
    }

  NestedType nested = 1;
}
```

Currently `GetMessageClassesForFiles()` will only return `NestedTypeMessage`, but miss `NestedTypeMessage.NestedType` (and any arbitrary level of nested definitions).

This is an unexpected deviation from the comment that says that it will find and resolve all dependencies.

PiperOrigin-RevId: 719854337
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant