Repository navigation
Keep the tabular CSV bridge out of the native IFC build - #49
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.
Move the existing CSV bridge and the
IfcModelimport/export methods into the source set for compatibility. The regular package preserves the assembly, namespace and signatures used by the CLI and library consumers. Update the optional tools links to reflect their NuGet preview availability.Verified the native engine and adapter on .NET 8 and 10, regular tests and pack, strict API comparison against main for both assemblies, and byte-identical CLI CSV on a synthetic IFC fixture.