Using 2.0, still unable to use Add command on schemas

[CraigRegester]

Using latest release and a package mapping that looks like this:

I go to Interoperability->HL7 Schemas, pick a custom schema we have and using the Source Control button (up next to Delete), I select 'Add' from the menu.

This is the error that immediately pops up:

If I look in the Source Control output, however, it seems to have worked....

Maybe related to #191? Since I have multiple file types pointed to the same output folder? Not sure...

[CraigRegester]

As a related aside, might be prudent to setup the default output folders for the File Type mappings to match what has been used for quite some time now in VS Code ObjectScript extension... e.g., /src/cls, /src/rtn, /src/inc, /src/oth

Makes it a lot easier for my more advanced developers to use the best of both worlds.

[CraigRegester]

Ok it partially works - it adds the global entry for the TSH but not for the item itself. And the file itself, in the git repository, is in a status of 'untracked'

(different file but same premise - I was trying a few things to try and ensure I wasn't causing the issue somehow.)

[isc-svelury]

This is happening because LUT and HL7 files have the same export path. It would have also happened if the LUT files had an export folder that was an ancestor folder of the HL7 files. It is a consequence of the way we match mappings currently. The only way I can think of to fix this behavior would be to check if the file extension matches the one in the mapping.

@isc-tleavitt would that be acceptable? We discuss a related issue in #176 and conclude that exporting "as-is" is the right thing to do, so ideally we shouldn't have files exported with a different extension than their own.

[isc-tleavitt]

@isc-svelury that would be acceptable as a fallback option.