Manuel Schmidt

Hey @Sam-el0, thanks a lot for PR #133! I will have a look

This would affect mainly the instance module, but there both XBRL and iXBRL parsing is affected since these are separate functions.

This change is now live in version 2.2.0

This could also apply to context id's (see #86)

This could also apply to missing or not locatable taxonomies. #112 #76

Hey @rahulsinghal11 , sorry for the late answer.. Thank you for the proposal! According to the [XBRL Specification](https://www.xbrl.org/Specification/inlineXBRL-part1/PWD-2013-02-13/inlineXBRL-part1-PWD-2013-02-13.html#d1e5045) an ix:nonFraction element must have a value.  That's probably the reason...

Yes, the current very deep structure of object instances is quite annoying. In the past I tried to fix this problem by creating a compile method that takes all information...

But yes, the code you provided is currently the best and only method to get the labels.

Yes, i also think that from a performance perspective this would not be a problem. If we could find a way to also "compile" the information from the relational linkbases...

This is working pretty well for now. But tomorrow I would like to test the change a little bit and add a method getLabel() to the class Concept. After that...