Add an editorconfig/other code style tool to maintain preferred standards

[cmjchrisjones]

The other day you mentioned your preferred standards around when it came to using directives, from what I gather it was

• Usings to be placed at the top of the file, before the namespace declaration
• System usings to be placed at the top of the usings section
• Any 3rd party or Framework usings to be shown next
• lastly, any internal references / usings places
• All of the above 3 categories are seperated by a blank line, for example

using System;
using System.Collections.Generic;

using Microsoft.Azure.WebJobs;
using Microsoft.Extensions.Logging;

using AwesumIO.Core.Common;
using AwesumIO.Core.Business;

namespace AwesumIO.Functions
{
    ...
    // code
    ...
}

I believe we can achieve consistency by using something like an editorconfig to ensure these guidelines are met - do you have any others from the top of your head you can think of, if you want to take this approach, EG

• trailing commas on object initialisation
• spaces between keywords and brackets (EG if(x == y) { } vs if (x == y) { }`
• We could make it so when rules are violated, the build fails, rather than warns, or vice versa

There's loads of options - just thought I'd raise an issue, and I might even take a stab at it over the weekend :)

[michaeljolley]

This would be a great addition! We might even want to look at adding a .prettierrc & .eslintrc to the portal project so that we're standardized in Vue as well.