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.

Sign up for GitHub

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

Jump to bottom

Decide on nullable reference behavior for generated code #5811

Open
JoshLove-msft opened this issue Jan 29, 2025 · 0 comments
Open

Decide on nullable reference behavior for generated code #5811

JoshLove-msft opened this issue Jan 29, 2025 · 0 comments
Labels
emitter:client:csharp Issue for the C# client emitter: @typespec/http-client-csharp

Comments

@JoshLove-msft
Copy link
Contributor

Currently, all generated code has nullable references disabled. But System.ClientModel has nullable references enabled. We should decide which direction we want to go and whether we should have a toggle to decide the behavior. The Azure plugin will need to generate with nullable references disabled.
@JoshLove-msft JoshLove-msft added the emitter:client:csharp Issue for the C# client emitter: @typespec/http-client-csharp label Jan 29, 2025
@JoshLove-msft JoshLove-msft changed the title Decide on nullable specification for generated code Decide on nullable reference behavior for generated code Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
emitter:client:csharp Issue for the C# client emitter: @typespec/http-client-csharp
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JoshLove-msft