-
Notifications
You must be signed in to change notification settings - Fork 27
feat(revit): CNX-188 extract material quantities out for all objects #184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(revit): CNX-188 extract material quantities out for all objects #184
Conversation
…t-for-all-objects-regardless
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## dev #184 +/- ##
========================================
- Coverage 8.44% 8.28% -0.16%
========================================
Files 238 239 +1
Lines 4597 4685 +88
Branches 516 534 +18
========================================
Hits 388 388
- Misses 4192 4280 +88
Partials 17 17 ☔ View full report in Codecov by Sentry. |
…t-for-all-objects-regardless
…t-for-all-objects-regardless
…t-for-all-objects-regardless
Converters/Revit/Speckle.Converters.RevitShared/ToSpeckle/Raw/MaterialQuantitiesToSpeckle.cs
Outdated
Show resolved
Hide resolved
…t-for-all-objects-regardless
* combines material and render material conversion and removes bad logic * simplifies caching logic * minor notes
…t-for-all-objects-regardless
…d converter & fixes a copy paste error
we can bring 'em back if we validate the need for them.
…t-for-all-objects-regardless
…objects-regardless' of https://github.com/specklesystems/speckle-sharp-connectors into claire/cnx-188-extract-material-quantities-out-for-all-objects-regardless
_materialCacheSingleton = materialCacheSingleton; | ||
} | ||
|
||
public RevitMaterial Convert(DB.Material target) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I somehow feel we need to cleanup a bit what's happening - the trigger is we're shuffling in visual display stuff
…t-for-all-objects-regardless
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minors
private readonly RevitMaterialCacheSingleton _materialCacheSingleton; | ||
private readonly DisplayValueExtractor _displayValueExtractor; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems like these dudes shouldn't be injected at all
/// <summary> | ||
/// | ||
/// </summary> | ||
/// <param name="target"></param> | ||
/// <returns></returns> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice doc
jokes aside, it might be good to explain why it is list of dict as key string as value object?
Adds material quantities to all revit objects. Smaple commit: https://app.speckle.systems/projects/93200a735d/models/1b29238359@ae1b38c9aa
This is done by mirroring behavior in V2, by:
Also fixes a bug from display value extractor for lighting fixtures that was preventing commits from being sent.
However, for post-september release we should seriously consider sending
MaterialProxies
instead of attached the material to every material quantity. Need to validate how this affect data workflows in powerbi, viewer, and excel.