WebUI: Import doesn't directly tell whether an import has failed #2996

New Issue

Animan8000 · 2025-11-05T07:24:55-08:00

Animan8000 commented

2025-11-05 07:24:55 -08:00

There's a couple of issues I've been noticing with Import (more about that in other Issues), one being the following:

If the user does a mistake like:

  "Affiliations": [
    {
      "Standing": 250,
      "Title": 0,
      "Tag": "CetusSyndicate"
    }
  ]

(basically missing the extra curly bracket at the very beginning and very end)

and imports it, there's nothing that even indicates that this has failed. On other parts of the WebUI e.g. Add Item: if you do a mistake there, then the thing is marked red, but here at Import there's nothing that directly indicates that something has went wrong with the import itself and that could become confusing for someone who uses it for the first time and blindly makes a mistake.

There's a couple of issues I've been noticing with Import (more about that in other Issues), one being the following: If the user does a mistake like: ``` "Affiliations": [ { "Standing": 250, "Title": 0, "Tag": "CetusSyndicate" } ] ``` (basically missing the extra curly bracket at the very beginning and very end) and imports it, there's nothing that even indicates that this has failed. On other parts of the WebUI e.g. Add Item: if you do a mistake there, then the thing is marked red, but here at Import there's nothing that directly indicates that something has went wrong with the import itself and that could become confusing for someone who uses it for the first time and blindly makes a mistake.

Sainan referenced this issue

2025-11-05 07:45:12 -08:00

WebUI: Import "Successfully Imported" despite error #2998

Sainan added the improvement label 2025-11-05 07:45:24 -08:00

Sainan referenced a pull request that will close this issue

2025-11-05 07:51:48 -08:00

chore(webui): inform the user of JSON parsing errors during import #3001

Sainan added the pr'd for label 2025-11-05 07:51:53 -08:00

Sainan closed this issue

2025-11-05 07:58:26 -08:00

Sainan referenced this issue from a commit

2025-11-05 07:58:27 -08:00