I've been making use of the excellent new "store_date" and "cover_date" fields in the issue object, and I've run into one minor problem with "cover_date":
One the website, it is possible (and in fact extremely common) to specify a "fuzzy" date, which does not include a "day" value, just a year and a month (or a quarter). However, the API always provides the cover_date as a non-fuzzy date, i.e. 2010-9-25. The problem with this is that there is no way to tell the difference between an actually fuzzy date (2010-9) and a specific date (2010-9-25). This means I have to arbitrarily assume all cover dates are either fuzzy, or all are specific.
Two straightforward ways that I can think of that would help me deal with this:
1) don't provide the day for fuzzy dates ("2010-9" vs "2010-9-25"), or,
2) provide an extra field in the date:
Thanks again for all the work you guys have been putting into the API lately!