调用的地方比较多,有办法在LoggingFilter中获取到调用的信息
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- backend-api-design
Research direction
Start by tracing the custom LoggingFilter and its WriteLogAsync method through the request made by App.Clients.UserService.RunRequestAsync(). Determine whether the caller information shown in the issue is available at that point; done means the issue has a confirmed approach or a clearly documented limitation, with any needed scope identified.
Written by the indexing model from the issue text.
Description
我实现了自己的LoggingFilter
想在 WriteLogAsync 中获取到是哪个地方调用的接口,比如
at App.Clients.UserService.RunRequestAsync() in D:\Repos\WebApiClient\App\Clients\UserService.cs:line 31
- Dominant language
- C#
- Stars
- 2.1k
- Forks
- 445
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnetcore/WebApiClient
-
question 等待反馈(needs feedback)
Difficulty 5/5 Over a week Newbie friendliness 25/100
dotnetcore/WebApiClient#279 · 3 comments ·
-
question 等待反馈(needs feedback)
Difficulty 4/5 3-5 days Newbie friendliness 25/100
dotnetcore/WebApiClient#274 · 1 comment ·
-
question
Difficulty 4/5 3-5 days Newbie friendliness 30/100
dotnetcore/WebApiClient#271 · 2 comments ·
-
在原有接口方法调用上添加其他参数的方案? Open等待反馈(needs feedback)
Difficulty 5/5 Over a week Newbie friendliness 20/100
dotnetcore/WebApiClient#264 · 1 comment ·
-
new idea
Difficulty 4/5 3-5 days Newbie friendliness 35/100
dotnetcore/WebApiClient#261 · 5 comments ·
All issues in dotnetcore/WebApiClient
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·