-
Notifications
You must be signed in to change notification settings - Fork 460
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
1.x branch Better Plugin Support #1485
1.x branch Better Plugin Support #1485
Conversation
Add the concept of a `CodeGenerator` and some building blocks to go with it so some of the boilerplate around writing plugins is provided. This is the start of the building blocks to make supporting Editions easier for any plugin (grpc) when that support lands as it will make a lot of the setup details hidden rather than having to be implemented by each plugin.
Before it would silently ignore the attempt, which might confuse users.
The build failures on upstream protobuf are known and I think they are working to resolve. |
Extend `CodeGenerator` to allow easy customization and generally provide what's needed for a `main()` so plugins don't have to reimplement everything.
If there are a lot files generated, this linear check could have become an issue.
589f501
to
ef34a25
Compare
The 5.0.3 and 4.2.4 breaks confuse me, I didn't even change those files. I wonder is something just happened to the swift docker images? |
Oh, those are just notes, they must always be there. But I am using another api that I guess is an issue. |
Looks like `#available` isn't enough for some api usage in the really old Swift versions, so add a fallback for that case also.
bd80516
to
32183da
Compare
CI passes now with the fix for FileHandle on Swift <5.1 (and upstream protobuf having been fixed) |
This is #1483, but for the 1.x release branch
There are two minor changes:
@main
serializeBytes
vs.serializedData
.