verify-translator

You can verify Zotero translators by running lint with npm, executing translator tests, and validating web, import, and search translator behaviors. This workflow prevents regressions by ensuring updates and lastUpdated timestamp changes are checked before pushing a PR.

Linting Zotero translators with npm checks syntax and code quality on new or updated translator files. It is applied during development and CI workflows to ensure that additions or modifications meet quality standards before PR submission.

To validate Zotero translator behavior in CI workflows, execute translator tests after running lint with npm. This process tests web, import, and search translators to catch regressions and ensures any modified translator file maintains correct functionality before PR creation.

Yes, you must update the lastUpdated timestamp when changes are made to Zotero translators. This verification process requires updating the timestamp alongside running lint with npm and executing tests to ensure modifications are properly tracked before PR submission.

Web, import, and search Zotero translators are validated to prevent regressions. The verification workflow runs tests and validates translator behavior across these types after every addition or modification to ensure correctness before submitting PRs.

Yes, you can automate Zotero translator verification in CI workflows by running lint with npm and executing translator tests. This repeatable, audit-ready process validates translator behaviors and prevents regressions during development before PR submissions.