"no" vs 0 represantation about py-xbrl HOT 2 CLOSED

As you have already correctly recognized, the fact "InventoryNet" in the iXBRL Instance document only holds "no" as value:

<ix:nonFraction 
  unitRef="U_iso4217USD" 
  id="F_000403" 
  name="us-gaap:InventoryNet" 
  contextRef="C_0001733257_srt[...]_20201231" 
  decimals="INF" 
  format="ixt-sec:numwordsen" 
  scale="6">
    no
</ix:nonFraction>

It is also true that the SEC's iXBRL viewer interprets this "no" value as 0.
The inline XBRL Specification 1.1 defines the ix:nonFraction as follows:

The ix:nonFraction element denotes an XBRL numeric item which is an element which is not of type, nor derived from type, fractionItemType [...].
https://www.xbrl.org/specification/inlinexbrl-part1/rec-2013-11-18/inlinexbrl-part1-rec-2013-11-18.html#sec-nonFractions

Since a nonFraction element should never be text, I think it would be really useful for the parser to replace the original value "no" with 0 (as you proposed).
I just wonder if there can be other text values which should be unconverted to numeric values.
The fact could also hypothetically contain the text value "zero", however I haven't seen this in real submissions yet.

from py-xbrl.

For numeric value I also saw these:

    elif val.lower() in [u'☒', 'true', 'yes']:
      val = True
    elif val.lower() in [u'☐', 'false', 'no']:
      val = False
    elif val.lower() in [u'—', '-']: # considered 0 for numeric values
      val = 0

Just make sure '☐', 'false' won't be 0. (like tick boxes)

from py-xbrl.