Ah I may have misunderstood - it looked like I would have to install a tool and add a target to my csproj - I thought you could wrap that up in the package so that it works with just a PackageReference
Oh, you are speaking about source generation for schema.graphql. I decided to keep it as part of the CLI because source generation still is pretty laggy in cases when a developer needs to access source-generated classes. Sometimes it can get stuck for a few seconds, and you need to wait until compilation errors disappear. For me, it is annoying. So, a separate call to CLI in the target solves this issue.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Ah I may have misunderstood - it looked like I would have to install a tool and add a target to my csproj - I thought you could wrap that up in the package so that it works with just a PackageReference
Oh, you are speaking about source generation for schema.graphql. I decided to keep it as part of the CLI because source generation still is pretty laggy in cases when a developer needs to access source-generated classes. Sometimes it can get stuck for a few seconds, and you need to wait until compilation errors disappear. For me, it is annoying. So, a separate call to CLI in the target solves this issue.