Hi team! Maintainer of _@tony.ganchev/eslint-plugin-header_ here.
I was checking the plugin's usage and notice the comment in the wrapper
you had to create about the issues with _oxlint_.
Good news is _@tony.ganchev/eslint-plugin-header_ supports _oxlint_ as
of v3.3.2. The behavior is similar to the change the wrapper introduces
by eliminating defaults but still keeps the schema and any additional
metadata in place.
This PR proposes bumping the version and eliminating the wrapper.
On a side-note, I've added this repository to the plugin's set of
ecosystem tests: https://github.com/tonyganchev/eslint-plugin-header/actions/runs/23719239156/job/69091357637
Best,
Tony
The detection didn't work properly in case the selected manga was in a different language than English or the current active translation.
In that case it didn't work because the translation for that locale wasn't loaded.
So to ensure that the translation exists for each language, we have to hardcode it.
Switch to "lingui" for better DX.
Tried to persist existing languages as much as possible.
Removed "vite-plugin-node-polyfills" because it's incompatible with "lingui"
* [Tooling] Create script to update dependencies
* Lock dependency versions
* Update dependencies
Wait for eslint related dependencies to be compatible with v9
* [Tooling] Switch to github gql api
* [Tooling] Credit all authors
* [Tooling] Add pr info from the commits associated pr
* [Tooling] Log unexpected commit format before throwing error
* [Tooling] Prevent running script without sha of last commit of previous release
* Create permanent subscriptions
The subscriptions have to be permanently open, otherwise, the cache gets outdated.
E.g. in case a view is open, which does not subscribe to the download updates, finished downloads are never received and thus, data of existing chapters/mangas in the cache get outdated
* [Codegen][Tool] Get latest data from cache for automatic chapter deletion after reading
The manga chapters query is on "standby" to prevent the reader from rerender in case the underlying query data updates, which would cause the reader to jump back to the beginning of the last read page.
Thus, when checking if the chapter should be automatically deleted, the data from the query can't be used, since it is outdated.
