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

[http-client-java] Java CodeGen should address the errors and warnings from TCGC #5575

Closed
3 tasks done
Tracked by #2070
lirenhe opened this issue Jan 13, 2025 · 1 comment
Closed
3 tasks done
Tracked by #2070
Labels
emitter:client:java Issue for the Java client emitter: @typespec/http-client-java

Comments

@lirenhe
Copy link
Member

lirenhe commented Jan 13, 2025

Clear and concise description of the problem

We need to empower our customers both internal and external to easily trouble shooting and fix spec issues that would block the CodeGen.

Today, TCGC could already do the check on the patterns and results from TypeSpec compiler and reports warning and errors for the unsupported case and invalid usage.

However, today our CodeGen didn't address those errors and warnings from TCGC in the implementation and in most cases would continue the codegen which would result in unexpected generated code & error. When that happens, the outcome would be difficult to trouble shooting.

Proposals:

  • Java CodeGen need to display those warnings and errors in the command line output instead of ignoring them.
  • Java CodeGen should properly address the errors and warnings from TCGC to provide a better user experience.

Checklist

  • Follow our Code of Conduct
  • Read the docs.
  • Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
@weidongxu-microsoft
Copy link
Contributor

TCGC diagnostics is reported via reportDiagnostics

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
emitter:client:java Issue for the Java client emitter: @typespec/http-client-java
Projects
None yet
Development

No branches or pull requests

2 participants