fix: remove invalid x- fields from Kafka bindings example

[wei123-web]

---

title: ""
---fix: remove invalid x- fields from Kafka bindings example

---

Related issue(s):
The ADEO Kafka example had invalid x- fields in Kafka bindings.
These fields are not allowed according to the Kafka binding JSON schema.
Removed x-key.subject.name.strategy and x-value.subject.name.strategy.

Related issue(s): #1164

---

[github-actions]

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[wei123-web]

Hello! AsyncAPI maintainers

This PR fixes the ADEO Kafka example by removing invalid x- fields (x-key.subject.name.strategy and x-value.subject.name.strategy) from the Kafka bindings.
These fields are not allowed according to the Kafka binding JSON schema.

Thanks for reviewing!

[wei123-web]

Hello! maintainers
Rebasing done — branch is up to date and ready for review.
Thank you!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[derberg]

Thanks for the contribution. I’m closing this PR because, while there is an existing issue, it was not approved or opened for contribution before the pull request was submitted.

Please make sure to follow the contribution guidelines, which explain when issues are considered ready for implementation and when pull requests are appropriate.

[wei123-web]

got it I’ll follow the contribution guidelines