Shish
8.3 doesn't seem to have huge benefits, so maybe one more release with 8.2 compatibility :thinking:
Do you have a minimal example of failing code so we can see what you're trying to do? As far as I understand composer's autoload mechanism, files listed in `files`...
Right now if we drop support for php8.1, then these "functions which have been safe since 8.2" will be detected as "has always been safe", and the pass-through wrappers will...
My thinking for _not_ marking these functions as deprecated is that if you're writing an app which needs to run on 8.3 and 8.4, then it would be annoying to...
Looks like the answer is "no", but I want this package to exist and be maintained - so I've [forked it](https://github.com/shish/safe), merged many of the outstanding pull requests (and fixed...
So where nearly all functions are documented in `/functions/.xml`, `idn_to_ascii` and `idn_to_utf8` are documented in `intl/idn/.xml` and so our code to find functions isn't finding them ðŸ˜
(I do wonder if it'd be worth having example code as actual code (either in an "examples" folder, or a "graphqlite-examples" respository), rather than random code snippets inside a markdown...
Sorry for the delay - that fix does look correct, and I am very confused as to why the current code isn't throwing more explicit errors o_O Specifically phpstan recognises...
So it looks like if _any_ part of the type signature is `mixed`, phpstan will ignore the whole thing - and because `source` is being set to `$_REQUEST["source"]` (which has...
So this extension was designed to be compatible with danbooru 1.0 in 2008, and it's kind of inherently a mess - I'm not familiar with the latest clients of this...