Product
Strawberry Shake
Version
15.0.0
Link to minimal reproduction
https://github.com/ChilliCream/graphql-platform/blob/main/src/StrawberryShake/CodeGeneration/test/CodeGeneration.Razor.Tests/__snapshots__/RazorGeneratorTests.Query_And_Mutation.snap#L1320
Steps to reproduce
Use Strawberry Shake to generate blazor query components
What is expected?
Operation Interface type used
What is actually happening?
Sample taken from the razor generation tests
public partial class UseGetBars : global::StrawberryShake.Razor.UseQuery<global::Foo.Bar.IGetBarsResult>
{
[global::Microsoft.AspNetCore.Components.InjectAttribute]
internal global::Foo.Bar.GetBarsQuery Operation { get; set; } = default !;
....
}
GetBarsQuery is used instead of IGetBarsQuery
This typically poses no issue until you try to mock the component for unit tests (Bunit)
Relevant log output
Additional context
No response
Product
Strawberry Shake
Version
15.0.0
Link to minimal reproduction
https://github.com/ChilliCream/graphql-platform/blob/main/src/StrawberryShake/CodeGeneration/test/CodeGeneration.Razor.Tests/__snapshots__/RazorGeneratorTests.Query_And_Mutation.snap#L1320
Steps to reproduce
Use Strawberry Shake to generate blazor query components
What is expected?
Operation Interface type used
What is actually happening?
Sample taken from the razor generation tests
GetBarsQueryis used instead ofIGetBarsQueryThis typically poses no issue until you try to mock the component for unit tests (Bunit)
Relevant log output
Additional context
No response