Error in testRules method calling "new WEBIFC.IFC4[category]()" on "IFCDRAUGHTINGPREDEFINEDCURVEFONT"

[LeonardIllerhaus]

Describe the bug 📝

Hello guys, hope I am right here..

I am trying to get the IfcFinder working finding properties and it´s values (still struggling). For that I am switching between different testfiles. One of them is exported in IFC 4. When the BasicQuery gets to work, the console throws this error:

I looked up the method in the index.mjs and added a console.log(line) to show me the specific ifc entity which cannot be created. It runs through the first ~250 lines with no problems, last log before the error: #257=IFCDRAUGHTINGPREDEFINEDCURVEFONT('continuous')

The Query breaks at this point. My understandig of the testRules method so far: It checks all kind of ifc files (2x3, 4, 4.3, ...) with ifc 4 category definitions for attribute names. This seems kind of static to me and some how it wont work on all ifc 4 definitions. Am I missing somthing?
Best Regards and massive Thanks for this project :)

Reproduction ▶️

Steps to reproduce 🔢

Try to run the IfcFinder on the attached file with a property query
DTV_5_beams.zip

System Info 💻

OS: Windows 10 10.0.19045
    CPU: (8) x64 Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
    Memory: 6.30 GB / 15.86 GB
  Binaries:
    Node: 16.13.0 - C:\Program Files\nodejs\node.EXE
    npm: 8.1.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 131.0.6778.205
    Edge: Chromium (129.0.2792.89)
    Internet Explorer: 11.0.19041.4355

Used Package Manager 📦

npm

Error Trace/Logs 📃

index.mjs:24158 Uncaught TypeError: rN[t] is not a constructor at e.testRules (index.mjs:24158:33) at e.findInLines (index.mjs:24411:32) at s.onload (index.mjs:24094:14)

Validations ✅

• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a repository issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
• Check that this is a concrete bug. For Q&A join our Community.
• The provided reproduction is a minimal reproducible example of the bug.