Work in Progress: Adding in a UE4 blueprintable enum for login type

[Sessional]

Hoping you'll be kind enough to provide a "50% code review" and set me on a different course if this isn't what you have in mind.

Left a few //TODO statements for places where I'm not sure what to do with them. (C++ Newby)

The goal: provide a drop down for "Type" in the blueprint node so that a user can specify how to do logins inside their game without leaving blueprint or replicating behavior.

Justification: While not mandatory, prettifies the example interaction with the Blueprint Request Login node. And makes it simpler to swap the mode of authentication in the example project.

[fastlorisstudios]

The biggest request would be code formatting, to ensure the project is maintained the same throughout.
No spaces after some declaration (if, switch etc) and its braces. Spaces within the braces. All {scope} brackets in-line (i.e. opening on a new line, never the same as the declaration). Tab alignment of declarations (makes scrolling down the file easier).

In the player controller, create a new function RequestLoginByType, with the parameters you've specified. In there, do the Type to String conversion and call the original. In the RequestLoginByType UFUNCTION declaration you can neaten this up with a Meta and rename it, so on the BP side it simply says "Request Login" for both.

[fastlorisstudios]

Much of the design approach(es) taken for this Plugin mimic the Steam OSS Plugin. As such, there is no Blueprint Library in that Plugin, so I don't think it appropriate for us to have one in this Plugin, either.

Your own question about including the .cpp needs resolving before a merge. You also have the header include in the PlayerController header - is this include necessary?

And again, formatting considerations. All {scope} braces vertically in-line is a minimum.