Use of correction authentication properties

[jaliyaudagedara]

Fix for sub-issue mentioned in #342

The first commit contains the fix, and the second commit is just formatting.

[cdavernas]

LGTM, cheers!

[cdavernas]

@JBBianchi Please review the Blazor code => indentation

[JBBianchi]

@jaliyaudagedara I'm not a big fan of Visual Studio default formatting for Razor code.

I'd rather use a more "logical" approach with indentation for each block, like you would do in normal C# code when you open a block.

An alternative version/additional guideline would be: "if an element attribute goes to a new line, the all attributes should be on a separated line". e.g.:

<input type="text" value="@authentication.Name" required placeholder="Name" title="The authentication name" class="form-control"
    @onchange="async e => await OnPropertyChangedAsync(nameof(authentication.Name), a => a.Name = (string)e.Value!)" />

vs

<input 
    type="text" 
    value="@authentication.Name" 
    required 
    placeholder="Name" 
    title="The authentication name" 
    class="form-control"
    @onchange="async e => await OnPropertyChangedAsync(nameof(authentication.Name), a => a.Name = (string)e.Value!)"
/>

Both are illustrated here: https://gist.github.com/JBBianchi/0cb212d3e93191fd267fd5a20ac1f206

[jaliyaudagedara]

@JBBianchi,

I am sorry, it makes sense, pushed a change.

and on,

"if an element attribute goes to a new line, then all attributes should be on a separated line".

definitely agree!

[JBBianchi]

@JBBianchi,

I am sorry, it makes sense, pushed a change.

and on,

"if an element attribute goes to a new line, then all attributes should be on a separated line".

definitely agree!

Don't be sorry, thanks for your contribution :)

[cdavernas]

LGTM! Many thanks ❤️