Error in entry key stops parsing all further entries about biblatex-csl-converter

[retorquere]

(or I assume it does, the parser spits out everything that follows -- which is a lot in this file -- to the console)

[johanneswilm]

The output is now in an error message that the client app can deal with as it sees fit. I don't know how much sense it makes to try to process more of the file if one entry is broken, as that entry will likely have to be fixed anyway, and then import is restarted.

[retorquere]

The problem for me is that I can't talk to the user. I've usually generated a note as part of the import that explained the probable location of the error. I can throw an error, but Zotero will just say "an error has occurred".

[johanneswilm]

I see. So you prefer importing everything you can.

What are the chances of Zotero allowing better feedback? What would the process for that be? If I were the user, I would get quite frustrated if it A) Imports only half of my sources and doesn't tell me why, or B) skips some sources and doesn't tell me why.

[retorquere]

I don't speak for them in any formal capacity, but my guess would be "pretty slim". Import is seen strictly as a migration mechanism as far as I can tell. But exporters have the same problem.

Yes, frustrating, which is one of the reasons I built in an automated error reporting facility. The user gets a cryptic error and the way to the logs is not very user friendly.

[johanneswilm]

Tested: It does not stop the import of other entries in the current version. Only the affected entry is not imported.