Detect CodeGen gaps by leveraging both server and client generation for TypeSpec-ToDo

allenjzhang / typespec-e2e-demo

TypeSpec Service CodeGen Demo

MIT License

0 stars 6 forks source link

Detect CodeGen gaps by leveraging both server and client generation for TypeSpec-ToDo #8

Open lirenhe opened 3 days ago

lirenhe commented 3 days ago

Generate the server code for TypeSpec-ToDo with some basic implementation.
Generate client code for Java, Python, JS & .NET and try to run them against service code.

Please help to detect gap by scanning the code and run some manual testing. Areas to verify: a. The behavior of different error code handling. b. Paging behavior. c. Basic CRUD operation could work E2E.

lirenhe commented 3 days ago

cc @ArcturusZhang , could you help with server generation and work with language owner to verify the client code E2E

ArcturusZhang commented 2 days ago

For dotnet generated library:

NoAuth is not working. This spec has @useAuth(NoAuth) on the Users namespace. But the generated Users subclient is actually not affected at all.
ApiKeyAuth<cache, "session-id"> is not quite working in the cache way.
The @visibility("none") property Validated is exposed in the client generated result (known issue for generator)
Pageable operations are not generated as pageable because pageable is not implemented for unbranded libraries.

weidongxu-microsoft commented 2 days ago

Java

Emitter only support service specify Auth configure in one place. The configure on root namespace takes effect. So NoAuth on Users does not work.
Error model is not generated. PR in progress.
Pageable operation is not generated as pageable. Design with architects pending.

msyyc commented 2 days ago

Python issues summary: https://github.com/Azure/autorest.python/issues/2934