I just looked over the .gitignore, there isn't anything I am going to move over, since the output dir we are using is schema/ and we do in fact want to keep it.
While AVIF may be supported by all modern browsers, is this something we can also say for certain for any local GUI app that might be integrating with ligmotes? It might be good to still have some sort of compatibility
ID of the user should imply this should be a string right? which is what I think the type should be, not User. Since it doesn't make sense to return all of the user metadata for every single emote query, which also requires fetching all of their emote sets. Deep fetching all of the data like this is going to make our HTTP requests incredibly expensive as we scale, and we should try to target minimizing the joins and requests we need to do to fulfill our API contract in most situations, unless all of the user metadata information is always going to be needed whenever an emote is queried.
personally, i hate having multiple .gitignores. sometimes there's weird wacky shit that gets ignored by some sub directory gitignore and its stupid to have to figure out which of the potential gitignores in the directory might be doing some wacky shit. i would prefer promoting things here that need to be to the root /.gitignore