Parsing Failures for Empty Fact Values and 'nil' Text in XBRL Documents about py-xbrl HOT 2 OPEN

Hey @rahulsinghal11 , sorry for the late answer..
Thank you for the proposal!

According to the XBRL Specification an ix:nonFraction element must have a value.

That's probably the reason why I never encountered issues with this on submissions from USA and UK.

However, since this is really easy to fix (as you also stated) I am happy to implement it in the next release.
Could you attach the XBRL file you encountered issues with (or send it to me via email)?
I always find it helpful to test the change on the failing XBRL document.

Thanks!

from py-xbrl.

Hi @manusimidt
Thank you for your willingness to implement the fix in the next release. I'm unable to share the exact document due to its confidential nature. However, I assure you that I have thoroughly tested the changes using a range of documents in large numbers.

These changes are non-disruptive and will not negatively impact any existing functionality and only add additional checks to prevent potential errors that would have otherwise anyway occurred. The modifications are careful enough to ensure stability and enhance the overall performance of the library.

If there's anything else I can do to assist you or contribute to further improving this library, please don't hesitate to let me know.
Thanks

from py-xbrl.