Import view - new file timestamps.

[mcwebtree]

When importing in new files, (class, mac, etc. I'll use CLASS for the sake of differentiating between the XML import file), the date of the import XML file is not really relevant. The comparison is between the last modified date on the existing CLASS, and the last modified date of the CLASS that is being imported.
Since the last changed date is in the XML file for each CLASS within the XML, why isn't that parsed as the import CLASS names are extracted from the file and used in the comparison.

I know it currently replicates the previous behavior of studio, but that made no sense when studio did it either!

[isc-bsaviano]

Hi @mcwebtree, you're right that this extension tried to exactly replicate Studio's behavior. Given that this feature was only added to avoid a gap for people moving from Studio and that implementing your requested enhancement is non-trivial (it requires IRIS-side changes) I doubt we will implement it. Pining @isc-rsingh in case he wants to comment.

[mcwebtree]

Why would it require IRIS side changes when all the information for the update is in the XML file that you're scanning already to extract the names?
I assume I'm missing something, but I don't know what.

[mcwebtree]

Please excuse the fact that I have no idea what language this is, nor have I looked at extension mods and have no idea what it is capable of, but it seems to me that what I'm asking for is basically the below mods.

file.documents.forEach((doc) =>
items.push({
label: doc.name,
moddate: {someDateFormattingFunction .TimeChanged}
picked: true,
detail: ${ doc.ts.toString() != "-1" ? Server timestamp: ${doc.ts.split(".")[0]} : "Does not exist on server" }, ${fileTimestamps.has(file.file) ? **Last Mod: ${moddate}** : ""},
file: file.file,
})
);

I dug a little further and now ah, I see! You have to go and get the parsed file list by sending the XML file to Iris, and it sends back a list of available files in the import file.

I assume that is what this does.
// List the documents in the XML files
const documentsPerFile = await api.actionXMLList(filesToList).then((data) => data.result.content);

In that case, I understand the need to amend Iris, but I still think its a valuable and worthwhile modification. Pulling out that file modified date and returning it will add significant value to the import function. Meaning the risk of unintended code change reversion is mitigated.

Regards
Mark

[isc-bsaviano]

Yes, you're correct. This extension sends the contents of the files to IRIS. IRIS does the listing and then sends back JSON with info about the contained documents. The REST endpoints is using standard IRIS APIs for loading XML files, and those don't extract the LastModified timestamp from the file when listing. I can see why this would be an improvement, but I still don't think we are going to do it. The bar for server-side changes, especially ones to features added for legacy support, is pretty high.