You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now it is not clear what 'recommended guidelines' (severity = 2) stands for. Who makes a decision to skip or to apply the rule? From my perspective, we can change the wording to 'The rule must be applied always except the cases when there is a significant reason not to do this' and give an example of using Async-postfix with controller's actions or Mediator's handlers. We also need to specify who is responsible for making such decisions (is it a project team or ream/tech lead).
The text was updated successfully, but these errors were encountered:
oleg-zaitsev
changed the title
What 'recommended guidelines' mean?
What 'recommended guidelines' means?
Dec 1, 2019
it's been a while since we discussed this topic last time, I suggest reviewing optional rules and either increasing their severity to 1 or removing at all. This will decrease number of rules that must be maintained and make it simpler to follow the guideline.
Well, it's questionable. Let's have some poll to find out in a broader auditorium?
Personally, I like the idea of keeping recommended guidelines, because they educate people to some extent. Maybe they should be kept as separate documentation though so that we are not limited to C# guidelines only.
Now it is not clear what 'recommended guidelines' (severity = 2) stands for. Who makes a decision to skip or to apply the rule? From my perspective, we can change the wording to 'The rule must be applied always except the cases when there is a significant reason not to do this' and give an example of using Async-postfix with controller's actions or Mediator's handlers. We also need to specify who is responsible for making such decisions (is it a project team or ream/tech lead).
The text was updated successfully, but these errors were encountered: