GitLab

- I put a lot more work here into the API
  - Now uses a bit better organization where the base param class
  is only going to enforce string contents. Implementations of
  specific kinds of parameters need to add their own datatypes and
  be sure to update the string value whenever the set method is
  called for their class. The parent class will take care of ensuring
  that anything written to this value (which is used directly in the
  generate step) is valid. Any higher level validations can then be
  taken care of by the higher level implementations, which shouldn't
  need to worry about the lower level validations.

- All of these new things really need test cases written for them
so that we can be sure that it works. It's going to get hairy looking
for bugs on the higher level classes if this doesn't have a solid test
foundation.

- just need to read each section and implement

- Adds a parameter class
- Adds a potential ParameterValue interface(?)
- Adds some new utils
- THIS WILL FAIL ON CI, srry I need to go to bed, so I'm committing
  what I've got.

- From here:
  - Test cases need to be written for the new parameter class
  - Test cases need to be written for the two new utils
  - Test cases need to be written for the changes to content line

- thats right, just got it set up so I can write the tests _first_

- Even better, both the code and the tests are in typescript!

- Needed to be using an array instead of one string.

- The individual properties such as param and value need to be defined as interfaces/classes of their own. This will impact how this is implemented in the end.

- Begins implementation of the ContentLine class as well as
  starts the util module.

- Should be clear to implement the content line interface.

- still playing around here to make it work. Nothing real is
  implemented just yet.

- Also adds working gulp configuration.

- Next steps are to flesh out all the properties and associated
  tests for the timezone.js file/object.

- This needs to be fleshed out properly in the unit tests before
  being implemented.

- After this update, this API will no longer support the old spec

- This is an API breaking change, so I'll be clearing out the broken
  test files as well.