-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Media Cache Handler #16992
Fix Media Cache Handler #16992
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interestingly this could have been done on purpose.
|
||
return Task.CompletedTask; | ||
} | ||
=> _mediaFileStoreCacheFileProvider.TryDeleteDirectoryAsync(context.Path); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we accepted the rule to use block body for methods, ctor and conversions. Only use expression body for properties and indexers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think there was an objection into using expression for one line like this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I looked at the editor config and watched the meeting. You are correct, for methods we "can" use expression bodies when it is on a single line.
Like fire and forget? If so, that would be done at the higher level not here. I don't think there is a reason to execute a task and return a completed task. Maybe I am missing something here |
No description provided.