Parse facts without value instead of ignoring them

[yen31]

Hi @manusimidt .. So .. I please look at this filing .. 0001193125-24-046160 which is a 40-F .. the expected number of facts should be 3396 as I see it .. however, the count I observed is 3394 .. Can you help me understand what is happening here ?

This is the link of that filing 0001193125-24-046160 .. this seems to be the case with other filings as well ..
py-xbrl .. v2.2.17

[yen31]

I have attached a screen shot of the debug console .. Please look at the count of facts as 3394 as seen below in the debug terminal

[manusimidt]

Yes, this is because of:

py-xbrl/xbrl/instance.py

Lines 436 to 438 in 9378e21

	# check if the fact has a value (some facts are like <us-gaap:Assets ... \>
	if fact_elem.text is None or len(str(fact_elem.text).strip()) == 0:
	continue

The filing contains empty facts. Specifically the following.

<ema:PaymentsRelatedToSharebasedCompensationPlan contextRef="FROM_Jan01_2022_TO_Dec31_2022_Entity_0001127248_us-gaap_PlanNameAxis_ema_RestrictedShareUnitPlanMember" id="ID_2734" unitRef="CAD" xsi:nil="true"/>

so py-xbrl ignores it. not sure if this is the best approach. In the past I just thought that if it contains no value its probably anyways not of use.

[manusimidt]

this is how its shown in the EDGAR xbrl viewer. its just displayed as nil in the text.

[yen31]

@manusimidt - Thanks for looking into this ... In my opinion, it will be helpful to process these and send them out to the client.. delegating the responsibility of such facts to the client thereby adhering to the complete integrity of a filing

[rj3185]

Hi @manusimidt .. Can you please remediate this bug for us ? I can see it Open ... so probably .. the code doesn't have a fix

[rj3185]

Hi @manusimidt .. Please let me know if we can fix this issue ? It would be awesome if we could :)