• Joined on 2023-07-08
zephyr closed issue ligmo/ligmo#16 2025-05-06 10:57:15 -04:00
decide the name of a collection of emotes
zephyr commented on issue ligmo/ligmo#16 2025-05-06 10:57:15 -04:00
decide the name of a collection of emotes

Every open PR now uses "emote set," so the decision is made and implemented.

zephyr commented on issue ligmo/ligmo#16 2025-05-06 10:55:48 -04:00
decide the name of a collection of emotes

I think the fact that both 7TV and BTTV use "emote set" means it's the correct choice by convention. That said, I had chosen list first because it's a much more common word in English. I also…

zephyr pushed to typespec at ligmo/ligmo 2025-05-06 10:53:20 -04:00
e3b61cb574 api: rename emote list -> emote set
4805480051 api: move route tags to op definitions
Compare 2 commits »
zephyr pushed to schema-updates at ligmo/ligmo 2025-05-06 10:38:34 -04:00
ddb5bf4964 schema: rename emote list -> emote set
zephyr pushed to typespec at ligmo/ligmo 2025-05-06 10:23:41 -04:00
371467b616 api: first round of pr feedback updates
zephyr commented on pull request ligmo/ligmo#20 2025-05-06 10:18:35 -04:00
read api specification

I also wonder about pagination. I've never needed to do it with APIs I've written, and I don't know at what sort of scale you generally start to care. TypeSpec has stuff built-in for paginating,…

zephyr commented on pull request ligmo/ligmo#20 2025-05-06 10:10:06 -04:00
read api specification

The DB has ban reason and unban time. As I said in the previous comment, I'll be looking into how to incorporate the latter with the correct visibility rules.

zephyr commented on pull request ligmo/ligmo#20 2025-05-06 08:31:39 -04:00
read api specification

This would also suggest that /users/{platform}/{platformID} should instead be /platforms/{platform}/users/{platformID}. Am I reading that right? Do you agree?

zephyr commented on pull request ligmo/ligmo#20 2025-05-06 08:29:30 -04:00
read api specification

ban is the reason they're banned, not the unban time. We'd only want to show the latter to the user themselves and to moderators. TypeSpec has some stuff to express that, but I have to read more…

zephyr commented on pull request ligmo/ligmo#20 2025-05-06 08:26:30 -04:00
read api specification

Intentional. There's no useful comment to add here.

zephyr commented on pull request ligmo/ligmo#20 2025-05-06 08:22:34 -04:00
read api specification

yeah i have no idea how to do this

zephyr commented on pull request ligmo/ligmo#20 2025-05-06 08:18:08 -04:00
read api specification

Going to wait on #18 to do this, just to avoid any chance of a merge conflict.

zephyr pushed to schema-updates at ligmo/ligmo 2025-05-06 01:16:07 -04:00
254993cb00 schema: use integer for emote color
0331ccb4cb schema: use _id suffix for id fks
Compare 2 commits »
zephyr commented on pull request ligmo/ligmo#20 2025-05-06 01:01:10 -04:00
read api specification

wrt #16, currently using "emote list." If we want "emote set" instead, we should decide that quickly.

zephyr created pull request ligmo/ligmo#20 2025-05-06 01:00:21 -04:00
WIP: api specification
zephyr commented on pull request ligmo/ligmo#18 2025-05-06 00:59:40 -04:00
Initalize go project

If we specify it in mise and don't specify it in go.mod, then the versions are free to disagree. Saying toolchain local should be effectively saying "use the version in mise."

zephyr pushed to typespec at ligmo/ligmo 2025-05-06 00:56:45 -04:00
59f6dc6ed5 api: add read api definition
106c58bb41 api: add typespec scaffold
Compare 2 commits »
zephyr created branch typespec in ligmo/ligmo 2025-05-06 00:56:45 -04:00
zephyr commented on pull request ligmo/ligmo#18 2025-05-06 00:55:09 -04:00
Initalize go project

If we want to specify the Go version with mise, should we also specify toolchain local in go.mod? (I would take that as a reason not to specify it with mise, personally.)