Closed mrx23dot closed 3 years ago
You are correct, this is a bug. The Facts where the parser fails use the value format: ixt:datemonthdayen
. According to the Specification the the format "Accepts months in full or abbreviated form, with non-numeric separator" (https://www.xbrl.org/Specification/inlineXBRL-transformationRegistry/REC-2011-07-31/inlineXBRL-transformationRegistry-REC-2011-07-31.html#sec-ixt-11).
This means the value could either be 'December 31' or 'Dec 31', the latter is currently not supported by the libary. I will implement a fix.
Parsing the following 2 URLs give date parsing exceptions.
Are they violating the standard or the lib should be able to handle them? (although it would be risky guessing the date)
CODI time data 'Dec 31' does not match format '%B %d' url = 'https://www.sec.gov/Archives/edgar/data/0001345126/000134512621000014/codi-20210331.htm'
MFA time data 'Dec 31' does not match format '%B %d' url = 'https://www.sec.gov/Archives/edgar/data/0001055160/000105516021000007/mfa-20210331.htm'