silverwind
silverwind
Keep it open, we still want to fix this and implement resizing on upload and ideally resize any existing oversized avatars.
Maybe try using dynamic `import()` for loading plugins? That should seamlessly work for both ESM and CJS.
Seconding the request for PaleMoon in the compat tables. Probably only worth it if its compat data can be determined in an automated fashion, though.
I hope some of the PRs there could be merged, currently it seems like a mere version bump.
Yes I'm guilty of not contributing, but I was more talking about https://github.com/eslint-community/eslint-plugin-eslint-comments/pull/20 😉.
Should `allow-undeclared-keys` be made the default? Dragonfly is advertized as "drop-in" replacement to Redis, but this is a behavorial difference that breaks this compatibility.
A colleague was prototyping [asynq](https://github.com/hibiken/asynq) with dragonfly and this was the first incompatibility they noticed. You can see some of the scripts they run [here](https://github.com/hibiken/asynq/blob/master/internal/rdb/rdb.go).
It still bothers the question: Why not make the default flags redis-compatible? Dragonfly advertizes with "Dragonfly is fully compatible with Redis APIs" but that is clearly not the case with...
I'm also seeing false-positive H25 (Tag seems to be an orphan) on this golang syntax: ```handlebars {{$link := printf "%s" $url $text}} ``` Apparently it's tripping on the escaped double...
Seems like a start, but it's definitely missing some features like wildcard (`*`) support in `no_proxy`. > I think that this feature should be treated as plugin and loaded by...