Add source generator that reads a JSON value as a const string at compile time. (OSOE-819) about helpful-libraries

[Piedone]

Yeah, I understood it as such. Just that we publish all of our open-source projects using package.jsons on NuGet, so that'll affect their NuGet publishing (e.g. https://github.com/Lombiq/Orchard-Chart.js, https://github.com/Lombiq/Orchard-Content-Editors, https://github.com/Lombiq/Orchard-Data-Tables).

[Piedone]

Hmm, very interesting! This would be especially useful for updates done by Dependabot.

[AydinE]

I've been looking into this issue and playing around with source generators as I've never worked on one before.
There are a few findings that I wanted to share here and get some feedback

The classes that will be marked with the attribute [ConstantFromJson("ChartJsVersion", "package.json", "$..['chart.js']")] will need to be marked as partial: also see Source Generators cookbook
I am assuming that it won't be an issue to mark them as partial but wanted to just call it out.

Also in order to make the package.json file accessible to the generator it would have to be marked as an "AdditionalFiles" in the .csproj as source generators do not have access to the filesystem directly.

I am setting this up as a separate project within this repo for now, let me know if there are any thoughts around that.

[Piedone]

Partial shouldn't be an issue, nor AdditionalFiles I think but the latter also affects NuGet publishing. Perhaps it'd only result in an unnecessary file being bundled in the package, which is not a significant issue, but I don't know if it can break anything else.

[AydinE]

Hey @Piedone,

The marking of the AdditionalFiles is actually for the projects that will use the generator not on the generator itself. So the consuming projects would have to mark those files in their own .csproj so that the generator can access them at compile time

[Piedone]

I get build errors locally with a fresh clone of OSOCE:

Build log.txt

Repeated builds also fail.

[Piedone]

The earlier OSOCE 509442daa9bdc7dc060d8a0196b8e803881af293 also shows this:

[sarahelsaig]

Considering that it works with dotnet but not with VS, perhaps this is a VS bug. Then @AydinE please make a bug report.