very fair point, it would probably be better to use the contain function
hm. i now i read this back, i don't like the potential for spoofed key IDs. uniq check should probably be user_id/key_id pair?
for anyone seeing this: this was already used everywhere...
this should be fixed by 8765491399b76a556c237b0c445cbadd253ce751 which has been built and deployed as develop
ok your solution probably isn't what we want to do here since we do actually pass an object as the third option most of the time
but i genuinely do not know why it's using a spread operator _at…
hm, so the first one implies that the third argument is an object
whereas the second is a variable argument function
I'll poke it one sec
thought it might be
wonder what dep had a breaking change
4211e05a75
Merge pull request 'status component: Fix repeater name overflowing' (#383) from yukijoou/akkoma-fe:fix-status-usernames into develop
3ff0f46b9f
Merge pull request 'Docs: Improve backup restore + fix warnings' (#554) from ilja/akkoma:docs_db_create_in_separate_commands into develop
