michaelhochriegl / fastlogr Goto Github PK

Currently the namespace of the extensions is hardcoded, which can lead to problems. Best would be to use the same namespace the class where the LogMessage is defined in.

Add tests that use the nuget package and execute the same tests as #4

Add a proper readme describing the purpose, installation and usage of the package.

Currently custom types are not supported due to missing the usings the class where the LogMessage is defined.

Solution: add all the usings of the parent class to the generated class.

The generated code should have the default text that this is generated content.
It also should enable nullable.

The publish of nightly packages to the Github nuget feed is broken right now.
Error reported:

{"error":"Your request could not be authenticated by the GitHub Packages service. Please ensure your access token is valid and has the appropriate scopes configured."}

Currently the generator doesn't properly support caching, hence it generates too often even when there is no need to do so.
LogMessageToGenerate should be spiced up to be cache-able.

Add benchmarks comparing the following logging approaches:

1. "Standard" logging using ILogger.LogInformation
2. Logging using the manual coded high-performance logging with extension methods
3. Logging using the MS source gen approach
4. Logging using FastLogr

Add tests that actually generate code and test the outcome

Currently the CI/CD pipeline pushes a nightly release once changes are merged to a develop branch. I think I will not use the dev branch at all and simply publish a nightly whenever somethings is merged to main.

Proper releases will still be pushed once a release on Github is created, so there is still a difference between nightly and proper pre/releases.