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
if(valueisnull)returnResult.NotFound($"Value with ID {request.ValueId} not found.");if(valueisnull)return;
CSharpier will always break after the if condition.
if(valueisnull)returnResult.NotFound($"Value with ID {request.ValueId} not found.");if(valueisnull)return;
Prettier keeps things on the same line if they fit.
Look into how common it is in the csharpier-repos to break after the if condition vs keeping things on the same line. If it seems to be more common I think we should not break after condition.
If it is a somewhat even split, I think it is worth possibly not breaking "simple" statements. The bare return above would be simple. The other example is possibly simple.
The text was updated successfully, but these errors were encountered:
Yeah, I was expecting that behavior too. Since csharpier is based on prettier, it should follow the same rules. I would appreciate if there was at least a configuration for this.
Given
CSharpier will always break after the if condition.
Prettier keeps things on the same line if they fit.
Look into how common it is in the csharpier-repos to break after the if condition vs keeping things on the same line. If it seems to be more common I think we should not break after condition.
If it is a somewhat even split, I think it is worth possibly not breaking "simple" statements. The bare
return
above would be simple. The other example is possibly simple.The text was updated successfully, but these errors were encountered: