Add Halo5-Stats Spartan Company endpoint.

[C-Kennelly]

Implements the Halo5.Stats "Company" endpoint and touches up some consistency in the original GetPlayerAppearance API, mostly swapping capitalization of field names from camelCase to match the API and other classes.

The referenced endpoint is documented at: https://developer.haloapi.com/docs/services/58acdf27e2f7f71ad0dad84b/operations/596968ade2f7f7051870d29f

This gist has some sample usage for the endpoint - https://gist.github.com/C-Kennelly/33d59b01db2a01201399cb41364e059c

Once again, I implemented identical unit tests to GetPlayerAppearance - covering the basics on matching expected URL, returning results that match the schema, and not throwing random exceptions. Probably could use some more tests here, if there's interest.

All unit tests were passing, though I think I missed the compile step that placed the JSON files in the /bin/debug folder and ended up doing copy-step that manually. If that's not IDE specific, you might run into the same problem when you run locally, so heads up.

[C-Kennelly]

Implements the Halo5.Stats "Company" endpoint and touches up some consistency in the original GetPlayerAppearance API, mostly swapping capitalization of field names from camelCase to match the API and other classes.

The referenced endpoint is documented at: https://developer.haloapi.com/docs/services/58acdf27e2f7f71ad0dad84b/operations/596968ade2f7f7051870d29f

This gist has some sample usage for the endpoint - https://gist.github.com/C-Kennelly/33d59b01db2a01201399cb41364e059c

Once again, I implemented identical unit tests to GetPlayerAppearance - covering the basics on matching expected URL, returning results that match the schema, and not throwing random exceptions. Probably could use some more tests here, if there's interest.

All unit tests were passing, though I think I missed the compile step that placed the JSON files in the /bin/debug folder and ended up doing copy-step that manually. If that's not IDE specific, you might run into the same problem when you run locally, so heads up.

[C-Kennelly]

Implements the Halo5.Stats "Company" endpoint and touches up some consistency in the original GetPlayerAppearance API, mostly swapping capitalization of field names from camelCase to match the API and other classes.

The referenced endpoint is documented at: https://developer.haloapi.com/docs/services/58acdf27e2f7f71ad0dad84b/operations/596968ade2f7f7051870d29f

This gist has some sample usage for the endpoint - https://gist.github.com/C-Kennelly/33d59b01db2a01201399cb41364e059c

Once again, I implemented identical unit tests to GetPlayerAppearance - covering the basics on matching expected URL, returning results that match the schema, and not throwing random exceptions. Probably could use some more tests here, if there's interest.

All unit tests were passing, though I think I missed the compile step that placed the JSON files in the /bin/debug folder and ended up doing copy-step that manually. If that's not IDE specific, you might run into the same problem when you run locally, so heads up.

[C-Kennelly]

Implements the Halo5.Stats "Company" endpoint and touches up some consistency in the original GetPlayerAppearance API, mostly swapping capitalization of field names from camelCase to match the API and other classes.

The referenced endpoint is documented at: https://developer.haloapi.com/docs/services/58acdf27e2f7f71ad0dad84b/operations/596968ade2f7f7051870d29f

This gist has some sample usage for the endpoint - https://gist.github.com/C-Kennelly/33d59b01db2a01201399cb41364e059c

Once again, I implemented identical unit tests to GetPlayerAppearance - covering the basics on matching expected URL, returning results that match the schema, and not throwing random exceptions. Probably could use some more tests here, if there's interest.

All unit tests were passing, though I think I missed the compile step that placed the JSON files in the /bin/debug folder and ended up doing copy-step that manually. If that's not IDE specific, you might run into the same problem when you run locally, so heads up.

[C-Kennelly]

Implements the Halo5.Stats "Company" endpoint and touches up some consistency in the original GetPlayerAppearance API, mostly swapping capitalization of field names from camelCase to match the API and other classes.

The referenced endpoint is documented at: https://developer.haloapi.com/docs/services/58acdf27e2f7f71ad0dad84b/operations/596968ade2f7f7051870d29f

This gist has some sample usage for the endpoint - https://gist.github.com/C-Kennelly/33d59b01db2a01201399cb41364e059c

Once again, I implemented identical unit tests to GetPlayerAppearance - covering the basics on matching expected URL, returning results that match the schema, and not throwing random exceptions. Probably could use some more tests here, if there's interest.

All unit tests were passing, though I think I missed the compile step that placed the JSON files in the /bin/debug folder and ended up doing copy-step that manually. If that's not IDE specific, you might run into the same problem when you run locally, so heads up.

[C-Kennelly]

Implements the Halo5.Stats "Company" endpoint and touches up some consistency in the original GetPlayerAppearance API, mostly swapping capitalization of field names from camelCase to match the API and other classes.

The referenced endpoint is documented at: https://developer.haloapi.com/docs/services/58acdf27e2f7f71ad0dad84b/operations/596968ade2f7f7051870d29f

This gist has some sample usage for the endpoint - https://gist.github.com/C-Kennelly/33d59b01db2a01201399cb41364e059c

Once again, I implemented identical unit tests to GetPlayerAppearance - covering the basics on matching expected URL, returning results that match the schema, and not throwing random exceptions. Probably could use some more tests here, if there's interest.

All unit tests were passing, though I think I missed the compile step that placed the JSON files in the /bin/debug folder and ended up doing copy-step that manually. If that's not IDE specific, you might run into the same problem when you run locally, so heads up.

[C-Kennelly]

Implements the Halo5.Stats "Company" endpoint and touches up some consistency in the original GetPlayerAppearance API, mostly swapping capitalization of field names from camelCase to match the API and other classes.

The referenced endpoint is documented at: https://developer.haloapi.com/docs/services/58acdf27e2f7f71ad0dad84b/operations/596968ade2f7f7051870d29f

This gist has some sample usage for the endpoint - https://gist.github.com/C-Kennelly/33d59b01db2a01201399cb41364e059c

Once again, I implemented identical unit tests to GetPlayerAppearance - covering the basics on matching expected URL, returning results that match the schema, and not throwing random exceptions. Probably could use some more tests here, if there's interest.

All unit tests were passing, though I think I missed the compile step that placed the JSON files in the /bin/debug folder and ended up doing copy-step that manually. If that's not IDE specific, you might run into the same problem when you run locally, so heads up.

[C-Kennelly]

Implements the Halo5.Stats "Company" endpoint and touches up some consistency in the original GetPlayerAppearance API, mostly swapping capitalization of field names from camelCase to match the API and other classes.

The referenced endpoint is documented at: https://developer.haloapi.com/docs/services/58acdf27e2f7f71ad0dad84b/operations/596968ade2f7f7051870d29f

This gist has some sample usage for the endpoint - https://gist.github.com/C-Kennelly/33d59b01db2a01201399cb41364e059c

Once again, I implemented identical unit tests to GetPlayerAppearance - covering the basics on matching expected URL, returning results that match the schema, and not throwing random exceptions. Probably could use some more tests here, if there's interest.

All unit tests were passing, though I think I missed the compile step that placed the JSON files in the /bin/debug folder and ended up doing copy-step that manually. If that's not IDE specific, you might run into the same problem when you run locally, so heads up.