• Joined on 2025-04-28
hamza commented on pull request ligmo/ligmo#20 2025-05-06 01:21:54 -04:00
read api specification

this should be /emote/{emoteId} (using whatever preferred case). If in the future we have /resource/{id}/subresource/{id} then there's a problem/ambiguity in terms of naming/inconsistency.

hamza commented on pull request ligmo/ligmo#20 2025-05-06 01:21:54 -04:00
read api specification

this should be plural. the vast majority of my personal preferences/reasoning coming from the google AIPs:

hamza commented on pull request ligmo/ligmo#20 2025-05-06 01:21:54 -04:00
read api specification

we should probably not be using the package-lock.json and be importing this into the pnpm workspace so that dependencies are deduplicated and we have a single lock file for the entire project. I can fix this up if you would like

hamza commented on pull request ligmo/ligmo#20 2025-05-06 01:21:54 -04:00
read api specification

The fact that typespec just defaults to "latest" for versions for things is insane

hamza commented on pull request ligmo/ligmo#15 2025-05-06 01:05:37 -04:00
schema: adjustments

Should we just use INTEGER and just use the RGB value instead of as a string? saves data at the very least

hamza commented on pull request ligmo/ligmo#18 2025-05-06 00:56:26 -04:00
Initalize go project

I'm not very familiar with toolchain tbh. is there a concern with toolchain local?

hamza commented on pull request ligmo/ligmo#18 2025-05-06 00:14:23 -04:00
Initalize go project

SERVE

hamza commented on pull request ligmo/ligmo#18 2025-05-06 00:12:46 -04:00
Initalize go project

add go = "1.24.2"

hamza commented on pull request ligmo/ligmo#18 2025-05-06 00:12:06 -04:00
Initalize go project

we might as well just make this 1.24.2

hamza commented on pull request ligmo/ligmo#18 2025-05-05 23:14:01 -04:00
Initalize go project

I personally of the opinion that having an env file that sets the values for each environment is better to go, much more portable and swappable over having to pass a long list of args (which can…

hamza commented on pull request ligmo/ligmo#18 2025-05-05 22:46:03 -04:00
Initalize go project

I don't like the idea that we automatically run the up migration every time the application starts up. Is this the best way to do it? I would prefer it was a separate command or something.

hamza commented on pull request ligmo/ligmo#18 2025-05-05 22:46:03 -04:00
Initalize go project

can we remove the elixir stuff

hamza commented on issue ligmo/ligmo#19 2025-05-05 22:19:03 -04:00
test

test comment

hamza closed issue ligmo/ligmo#19 2025-05-05 22:18:58 -04:00
test
hamza opened issue ligmo/ligmo#19 2025-05-05 22:18:53 -04:00
test
hamza created pull request ligmo/ligmo#13 2025-05-04 04:16:57 -04:00
WIP: initial dashboard content
hamza pushed to initial-ui at ligmo/ligmo 2025-05-04 04:16:45 -04:00
6713c1619a initial dashboard content
2c81978ea2 schema: initialize database (#12)
0d25fe733f meta: add .vscode configuring elixirls (#4)
Compare 3 commits »
hamza approved ligmo/ligmo#12 2025-05-03 19:09:19 -04:00
schema: initialize database
hamza commented on pull request ligmo/ligmo#12 2025-05-03 19:05:23 -04:00
schema: initialize database

typo

hamza commented on pull request ligmo/ligmo#12 2025-05-03 18:42:45 -04:00
schema: initialize database

I agree with your todo. I can't think of any benefit of having users with no name