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

CodeGenerator support for response edition information. #1558

Merged
merged 1 commit into from
Feb 26, 2024

Conversation

thomasvl
Copy link
Collaborator

  • Add api to get supported editions range.
  • If the generator signals editions support, add the range into the generation response.
  • Make the protos Editions enum Comparable since the docs document it and it then will allow other code paths to do version comparisons.

@thomasvl thomasvl requested a review from allevato February 26, 2024 17:39
- Add api to get supported editions range.
- If the generator signals editions support, add the range into the generation
  response.
- Make the protos Editions enum Comparable since the docs document it and it
  then will allow other code paths to do version comparisons.
@thomasvl thomasvl force-pushed the response_editions_plumbing branch from 8556867 to 483a7aa Compare February 26, 2024 17:44
@thomasvl
Copy link
Collaborator Author

Oops, pulled back some of the extension apis and just marked them deprecated, so help eventual adoption.

@thomasvl thomasvl merged commit 322b53d into apple:main Feb 26, 2024
10 checks passed
@thomasvl thomasvl deleted the response_editions_plumbing branch February 26, 2024 18:00
thomasvl added a commit to thomasvl/swift-protobuf that referenced this pull request Feb 27, 2024
This backs out the plugin public interface that was just added in apple#1558. My
local prototype was working using this, but I wasn't looking at supporting
plugin specific features yet, and in doing that, I realized the same edition
min/max information will also come in via `FeatureSetDefaults` and will have to
be in sync. So dropping the interface until I plan that support out better.
thomasvl added a commit that referenced this pull request Feb 27, 2024
This backs out the plugin public interface that was just added in #1558. My
local prototype was working using this, but I wasn't looking at supporting
plugin specific features yet, and in doing that, I realized the same edition
min/max information will also come in via `FeatureSetDefaults` and will have to
be in sync. So dropping the interface until I plan that support out better.
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.

2 participants