Vitaliy K
Vitaliy K
Please add job execution pipeline to allow applying cross-cutting concerns to job handlers. Something similar to ASP.NET Core middleware https://docs.microsoft.com/en-us/aspnet/core/fundamentals/middleware/write?view=aspnetcore-5.0
I'd recommend something like https://github.com/damianh/LibLog instead
I assigned following scopes, it works 1. `repo:status` Access commit status 2. `repo_deployment` Access deployment status 3. `public`_repo Access public repositories
`public_repo` is enough for public repositories. Not sure about private. To create token navigate to https://github.com/settings/tokens/ (or _Settings/Developer_ settings and select _Personal access tokens_)
@canton7 As I understand binary response support was not implemented yet. Are there any plans to do it? Would be great if serializer/deserializer will have direct access to request/response stream...
+1 for forking and publishing as a separate package. Maintaining another package is an overhead, but add more flexibility
@leandro86 Using DI instead would be a better approach. I had a lot of issues with HttpContext based approach when decided to move some code to run in background thread.
need to get all dependencies upgraded
Hi, sorry for delay ``` [Xunit.FactAttribute] public async System.Threading.Tasks.Task $FactMethodName$() { $END$ } ```