Simplifying development/testing

[Saalvage]

The way the repository is currently set up, it seems that in order to test your changes, you need to set up a local nuget repository in which you put your new library builds, this being required for every single build.

I think it would be desirable to replace the PackageReferences in the testing projects with ProjectReferences, which would automatically reference the latest build without needing to deal with local nuget repos at all.

I tried doing this, but quickly ran into the following build errror: Could not load file or assembly 'Scriban, Version=6.0.0.0.
By partly reverting the changes in 4ba4b8c (re-enabling PackageScribanIncludeSource and IncludeAssets) I made some progress, with only CsvTextFieldParser causing the same error now.
I managed to make everything compile by commenting out all code whose generators depend on CsvTextFieldParser (since it doesn't seem to provide an equivalent to PackageScribanIncludeSource).
While this works for me, it's not exactly convenient and I feel like this might be a general issue for people seeking to contribute to the library.

I'm not sure what exactly the intended workflow is and maybe I am missing something here! Please do let me know if so.
It's also entirely possible that this is a fundamental limitation of source generators in some way (considering they're not really fully mature) in which case I don't think there's much that can be done.
Either way, I feel like some documentation of how you are supposed to build/work on the library would be really helpful!

Thank you!

[Cat-Lips]

Yeah... There are a few caveats with the tests... Could definitely could do with some documentation. I'll get on that.

In the Nuget Package Manager (Visual Studio), you can change the Package Source to SourceGenerators.Release to test the current (release) build. This is configured in nuget.config. Godot doesn't seem to recognise this file so you can't run build/run the test from the Godot Editor with a local package.

I think it's possible to reference the project directly, but one would have to explicitly include all dependencies. (These are marked as private in the analyser so they don't add to or conflict with any downstream dependencies). But then we would also need to ensure that everything works when the package is installed and run as a separate nuget. Maybe we could create a symlink to the nuget cache, or check if godot has any C# specific build options we can customise?

[Saalvage]

I wasn't aware of this nuget source, that's really helpful!
Personally, that's fine enough for me, it'd be nice to have a cleaner integration, but it doesn't seem trivial and since it's working fine as is I think it should be ok for now.