Adding .devcontainer configuration files will make it easier for users of VSCode and Docker to set up their development environment. See this VSCode extension for more details.

There is currently only one test that I created as a template. More tests should be added to have better code coverage. The project uses mocha and chai for its tests. Input from somebody who has used those frameworks previously would be appreciated. Investigating this issue may result in some code refactoring considerations.

The official link naming must have changed. Links to official halo api within our own documentation are invalid.

Example

current:
https://developer.haloapi.com/docs/services/58acdf27e2f7f71ad0dad84b/operations/58acdf28e2f7f70db4854b36
actual:
https://developer.haloapi.com/docs/services/58acdf27e2f7f71ad0dad84b/operations/Halo-5-PC-Match-Result-Custom?

The project's Node version includes https and it is not necessary to have it installed as a dependency.

The current action that is run on a pull request only performs linting. This should also perform npm run test. This could wait until #2 is closed.

I am using this starter workflow to publish to npmjs.com and this repository's package registry. The publish to npmjs.com works, but the publish to github fails. This needs to be investigated to figure out why. Our version of the file can be found here.

The current structure of the code is primarily due to it being inherited from the previous project. I would like to restructure it in such a way that allows for easily adding new games (i.e. Halo Infinite) or categories (stats, metadata, ugc, etc). I am currently trying to research options but I don't have any existing knowledge of how to implement that sort of architecture.

I'd like to take advantage of the strict structure of TypeScript. This might also help resolve the new structure mentioned in #3.