Initial setup instructions improvement

The wiki states for the the initial setup to add a target in the project file so it’s rebuild every time before compile:

<Target Name="GenerateQLClient" BeforeTargets="BeforeCompile">
    <Exec Command="dotnet zeroql generate --schema .\schema.graphql --namespace TestServer.Client --client-name TestServerGraphQLClient --output Generated/GraphQL.g.cs" />
</Target>

As the generated client is not declared as output it can lead to build issues when the generated file is not existing already. This can be improved by declaring the output of the exec task and adding an item group:

    <Target Name="GenerateQLClient" BeforeTargets="BeforeCompile">
        <Exec Command="dotnet zeroql generate --schema .\schema.graphql --namespace TestServer.Client --client-name TestServerGraphQLClient --output Generated/GraphQL.g.cs" Outputs="Generated/GraphQL.g.cs">
            <Output ItemName="Generated" TaskParameter="Outputs" />
        </Exec>
        <ItemGroup>
            <Compile Include="@(Generated)" />
            <FileWrites Include="@(Generated)" /> <!-- For clean to work properly -->
        </ItemGroup>
    </Target>

Now the generated file doesn’t need to exist when building and also doesn’t have to be committed.

[byme8]

The generated client would be stored inside ./obj/ZeroQL folder. So it will never appear in the solution. However, you still have access to generated classes.

[byme8]

Checkout version 6.0.0-preview.1. I added additional targets to the Nuget package. Now it automatically looks for the ZeroQL config file and executes CLI on the build. Here the full documentation