Import / Export XML

[mcwebtree]

Is there a way to have a preview/confirmation screen of the export / import XML function?
In Studio, when you export you can see a list of files names you're going to export.
When you import you get to see file modified dates and select which files you want to import.

I tried to export a single class file, and it decided to export an entire subfolder, (x.y.cls was wanted, x.y.cls and x.y.*.cls was exported. probably a niche naming coincidence).
I tried to import the XML onto another server and it failed.
I tried to import it in Studio and saw all the unneeded files, selected the one I wanted, and imported fine.

Thanks

[isc-bsaviano]

Here's a link to the documentation on working with legacy XML files. Please let me know if you have any questions. https://docs.intersystems.com/components/csp/docbook/DocBook.UI.Page.cls?KEY=GVSCO_xml

[mcwebtree]

Hi
I tried again to import and ended up with this contradiction

I'm guessing this is a display bug, but it explains why I couldn't see the details when I did a single file upload the first time.
Only if I put something into the filter that I know to exist does it update the view to display all the files.

Regards

[mcwebtree]

In case it's not clear in the above image due to the redaction, the filename is long enough that it fills the entire first row, obscuring the first file space, pushing the rows down, but the drop down is set to only be big enough for 3 rows, (I assume), so the 3rd file disappears off the page.
Additionally with further tests, it seems if the filename is a little shorter, it does display the first character of the filename in the first slot but no other details can be seen on the first row.

[isc-bsaviano]

@mcwebtree I tried to reproduce that issue, but couldn't. I can see how VS Coder might render things strangely if the file path is very long. If you try the import with a shorter file path, does it render OK?

[mcwebtree]

Rendering OK is a relative term, it starts to eat away at the first row very quickly.

[isc-bsaviano]

Thanks for the screenshot. I bet the VS Code core team didn't intend for these "sepraator" strings to be so long. I could change this to only show the file name instead of the whole path. If there are two files with the same name I can show the containing directory as well.