Skip to content

Conversation

@ehsavoie
Copy link
Collaborator

Description

Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

  • Follow the CONTRIBUTING Guide.
  • Make your Pull Request title in the https://www.conventionalcommits.org/ specification.
    • Important Prefixes for release-please:
      • fix: which represents bug fixes, and correlates to a SemVer patch.
      • feat: represents a new feature, and correlates to a SemVer minor.
      • feat!:, or fix!:, refactor!:, etc., which represent a breaking change (indicated by the !) and will result in a SemVer major.
  • Ensure the tests pass
  • Appropriate READMEs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

@ehsavoie ehsavoie requested review from fjuma and kabir November 24, 2025 14:41
@ehsavoie ehsavoie force-pushed the updating_payloads branch 2 times, most recently from fb75b4d to 729bc88 Compare November 24, 2025 14:51
@fjuma
Copy link
Collaborator

fjuma commented Nov 24, 2025

It might be good to add some info in the PR description or commit message to indicate the commit hash that was used when copying the .proto file to this repo.

@ehsavoie ehsavoie force-pushed the updating_payloads branch 3 times, most recently from 431152c to e879e8c Compare November 24, 2025 15:54
ehsavoie and others added 4 commits November 25, 2025 09:51
- a2a.proto from commit b0784199543eebf2e95dcb02e9336cb213923506
- use "Dskip.protobuf.generate=false" to generate source code from
  a2a.proto

Signed-off-by: Emmanuel Hugonnet <[email protected]>
The spec-grpc classes are ugly, and we can't let users use them.
When using MapStruct an effort has been made to not use 'manual'
conversion (i.e. a 'default' implementation of the Mapper interface methods).

When automatic conversion happens, when the spec-grpc and spec classes differ
a compile error will be raised. Which in turn helps us keep our manually
generated spec classes in sync with the spec-grpc ones.
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.

3 participants