UILD-692: Mark import as failed when no resources are imported

[pkjacob]

Mark import as failed when no resources are imported

[github-actions]

Jest Unit Test Results

0 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ❌ ±0 

Results for commit 7aed81c. ± Comparison against base commit 982a5e7.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[zepheiryan]

This seems to me like it should either be a special case or not considered a problem.

Whether uploading a file with nothing in it or a file with only duplicates of existing resources, there are no correctable errors encountered from the round trip from front to back to front again. This seems like success: “we did exactly what you asked.” If we think an empty log or log full of duplicate notices isn't explicit enough, then “we did exactly what you asked but it was an empty graph” seems more appropriate than “we failed and you should look into what went wrong” - there’s nothing the user can actually change to get a different outcome.

[pkjacob]

This seems to me like it should either be a special case or not considered a problem.

Whether uploading a file with nothing in it or a file with only duplicates of existing resources, there are no correctable errors encountered from the round trip from front to back to front again. This seems like success: “we did exactly what you asked.” If we think an empty log or log full of duplicate notices isn't explicit enough, then “we did exactly what you asked but it was an empty graph” seems more appropriate than “we failed and you should look into what went wrong” - there’s nothing the user can actually change to get a different outcome.

Thank You. I will look into this next week.