Repository navigation
Read nested Extensible Storage in projects and loaded families - #278
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #15
Changes
Element.ExtensibleStorageand full JSON, including in RVT and RFA files with 32-bit element IDs.RevitFileInfo.EmbeddedFamilyExtensibleStoragefor elements in loaded family documents. The content key and saved element ID identify the owner. Embedded records use their own family schemas when present.Revit verification
Compared schema IDs, owning elements, nested values, and applicable element references from the saved files with the Revit API. For embedded records, the Revit reference came from
Document.EditFamily.Direct Revit 2024 and 2025 launches were blocked by an unsigned add-in prompt. The comparison used Revit 2027.2 to open those saved layouts without saving them.
Regression checks