You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disabling this setting can be useful when properties are not needed or handled independently. Skipping this step will then reduce computation time.
Reproduction ▶️
No response
Steps to reproduce 🔢
...
ifcLoader.settings.includeProperties = false;
...
const group = await ifcLoader.load(buffer);
const props = group.getLocalProperties();
// the properties are present, but they shouldn't
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.
Describe the bug 📝
It seems that the setting ifcLoader.settings.includeProperties isn't respected when loading an IFC file.
It could be that the bug is in the code below.
It looks like when calling ifcLoader.load(), IfcJsonExporter is used without checking this setting.
Source file:
https://github.com/ThatOpen/engine_components/blob/main/packages/core/src/fragments/IfcLoader/index.ts
Code:
Disabling this setting can be useful when properties are not needed or handled independently. Skipping this step will then reduce computation time.
Reproduction▶️
No response
Steps to reproduce 🔢
System Info 💻
Used Package Manager 📦
npm
Error Trace/Logs 📃
No response
Validations ✅
The text was updated successfully, but these errors were encountered: