Draft
Conversation
Contributor
Author
|
I had issues trying to create tests for importing line styles in itwinjs-core, so created them here for. Problem was mostly due to not knowing how to properly export/import all necessary data from src to target DB, and the imodel-transformer repo does this for us. |
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
1 participant
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.
Test for importing regular and compound line styles when preforming process all on imodels with line style elements. Tested on changes from:
iTwin/imodel-native#1024
Original issue:
#231
This pr is targeted for itwinjs-v5 as when I was working on the changes in imodel-native it was easier to work on imodel-native main vs release branches. Should these changes be needed in 4.x we can back port the native changes and these tests