-
Notifications
You must be signed in to change notification settings - Fork 790
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
Required changes for 3.0.0 preview3 #112
Conversation
test/Grpc.AspNetCore.Server.Tests/GrpcEndpointRouteBuilderExtensionsTests.cs
Outdated
Show resolved
Hide resolved
src/Grpc.AspNetCore.Server/Internal/HttpContextServerCallContext.cs
Outdated
Show resolved
Hide resolved
src/Grpc.AspNetCore.Server/Internal/HttpContextServerCallContext.cs
Outdated
Show resolved
Hide resolved
test/Grpc.AspNetCore.Server.Tests/GrpcEndpointRouteBuilderExtensionsTests.cs
Outdated
Show resolved
Hide resolved
test/Grpc.AspNetCore.Server.Tests/GrpcEndpointRouteBuilderExtensionsTests.cs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approved, but we need to figure out the question of depending on daily build vs. depending on a released version.
We definitely need a test that makes sure that everything is working against the latest released version (preview2 for now, preview3 soon). I'm not sure about the importance of testing against the unreleased version of .NET core - that depends on how often we will need access to new APIs and fixes (hopefully not often because the thing needs to work for users with preview3 anyway?). If we need both, we should have two tests.
…nsionsTests.cs Co-Authored-By: JunTaoLuo <[email protected]>
…nsionsTests.cs Co-Authored-By: JunTaoLuo <[email protected]>
cc @halter73 |
I noticed a few changes in preview3 and updated our code accordingly.