LT-10590: Include all metadata fields in flextext export#485
Conversation
|
Why was this necessary now? |
|
I needed it in order to do an end-to-end unit test (TestMetaDataRoundtrip). The test framework already had a unit of work. |
|
Ok, this code is very old and pre-dates the nice way of doing this. Instead of the try\finally We want to wrap all this code in a UndoableUnitOfWorkHelper.DoUsingNewOrCurrentUOW() That will eliminate the need for your variable and make this consistent with the current state of the art. |
jasonleenaylor
left a comment
There was a problem hiding this comment.
@jasonleenaylor reviewed 6 of 11 files at r1, 2 of 2 files at r2, 1 of 1 files at r3, all commit messages.
Reviewable status: 9 of 11 files reviewed, all discussions resolved
I extended FlextextInterlinear.xsd to allow items to have guid attributes that can point to structured data in the element. I then changed BirdInterlinearImport.cs and InterlinearExport.cs to import and export all of the metadata, including the notebook record and genres. The notebook record is stored in , but only the fields that are visible in the info field. Genres and other possibilities are stored with a guid and a name, but the possibilities themselves are not stored in . InterlinearObjects contains the mapping between ICmObjects and xml. It is shared between BirdInterlinearImport.cs and InterlinearExport.cs.
This change is