Description, issue
Currently...
- carrier formatting is a mess (when to use short-hand ("CH") vs longhand ("Chubb"), lower-case vs. upper-case vs. sentence-case;
- carrier objects are currently defined as dicts in more than one spot;
- code duplication is most prevalent because of this issue
- no current method exists to even represent a carrier as a string, which would be more convenient at times.
Solution
Alternatives
Dicts carrying varying data around, which could be improved with NamedTuples, which then can be improved by just using another class object to also have accompanying methods for more extensibility/convenience.
Description, issue
Currently...
Solution
Alternatives
Dicts carrying varying data around, which could be improved with NamedTuples, which then can be improved by just using another class object to also have accompanying methods for more extensibility/convenience.