Hi, I have a solution where NCrunch cannot build my Graphql client project.
Also the unittests project does not reference that project, but NCrunch does not attempt to build it.
Where could I provide the sample project please ?
Thx,
Dirk
Remco NCrunch Developer
#17491
11 Jul 2024 13:09 UTC
Hi Dirk,
We've done no work to support this kind of project type.
You can submit small samples in ZIP form through the NCrunch contact form.
We've done no work to support this kind of project type.
You can submit small samples in ZIP form through the NCrunch contact form.
Sample submitted.
It's a regular project, with a regular nuget library.
It's a regular project, with a regular nuget library.
Remco NCrunch Developer
#17493
11 Jul 2024 23:15 UTC
Thanks for sharing this sample.
The problem is caused by a missing dependency. In the project file, some of the Graphql files are explicitly removed from the project:
<ItemGroup>
<None Remove="GetAllOthersV1.graphql" />
<None Remove="GetOneContractVersionV1.graphql" />
</ItemGroup>
As a result, NCrunch doesn't copy them to the workspace when building the project. This causes the build to fail with a very obscure error.
You'll either need to avoid removing these files, or add them to NCrunch's 'Additional files to include' setting.
The problem is caused by a missing dependency. In the project file, some of the Graphql files are explicitly removed from the project:
<ItemGroup>
<None Remove="GetAllOthersV1.graphql" />
<None Remove="GetOneContractVersionV1.graphql" />
</ItemGroup>
As a result, NCrunch doesn't copy them to the workspace when building the project. This causes the build to fail with a very obscure error.
You'll either need to avoid removing these files, or add them to NCrunch's 'Additional files to include' setting.
Thanks. That was the culprit. I would have never known that from the current ncrunch output. I had to contact you through this forum to find out. Maybe something that could be improved ? (It's an excellent product and delivers great quality - don't misunderstand me ;)
Remco NCrunch Developer
#17496
15 Jul 2024 06:43 UTC
Where we can, we do try to get NCrunch giving useful error messages.
In this particular case, the error was coming from a nuget package - not from NCrunch. The only way for us to improve on this error would be to introduce special handling for just this Nuget package. Given that there are a lot of Nuget packages out there, you can probably understand our limitations. If it hits this forum a lot, then we may end up doing just that.
In this particular case, the error was coming from a nuget package - not from NCrunch. The only way for us to improve on this error would be to introduce special handling for just this Nuget package. Given that there are a lot of Nuget packages out there, you can probably understand our limitations. If it hits this forum a lot, then we may end up doing just that.
Post a reply
Log in to reply.