ContentCategory enum and corresponding category fields
kkharma opened this issue · 2 comments
kkharma commented
there are a number of fields (cat, bcat, etc.) that refer to list 5.1, which is a ContentCategory enum. however, all of these fields are typed as string. should they not be typed as ContentCategory?
opinali commented
That's a good idea; the spec uses ints or strings everywhere for these things but we can always use a higher-level type like enum in the model and then translate in the JSON serializer. It seems the ContentCategory fields are the only ones that missed this improvement, will fix this next release.
opinali commented
Fix will be in 0.8.1 soon.