pull down to refresh
It isn't hard. Mostly just not as need-to-have as some other things. We've lived beyond our naive stats collecting for sure. Advances should come sooner rather than later after some prereqs are done.
Where should I look for the analytics part of the codebase? I feel like this is something I could potentially contribute towards.
We have some materialized views that crunch them periodically e.g. permalink to user_stats_days
This part of the project is relatively unapproachable tbh. There's a lot of implied context (bad) in the DB schema. I don't want to scare you, but in case you're confused, it's our fault.
Following up on this... does this mean prisma/migrations/20240710001134_user_stats_refine/migration.sql was manually created? Because I couldn't find user_stats_days defined except in these migration files.
Sorry if dumb question, I am not familiar with prisma, but I thought the migrations are automatically managed.
Also, if you prefer that I move dev discussion to another channel, lmk. I didn't want to pollute the github issues / discussions threads unnecessarily if this is a dumb question.
This isn’t a dumb question. To modify ‘user_stats_days’ you’ll need to replace the function by performing another migration.
‘sndev prisma migrate dev —create-only’ will create an empty migration.
prisma’s docs are going to be the best place to learn about this stuff.
GitHub discussions would be great for these questions because other folks can chime in - and find them if they have the same questions.
Dumb questions are more than welcome!
Thanks I'll post future questions in GitHub discussions
I'll take a look if I have time (I probably won't, or will take a long time to get around to it, but the desire to contribute is there)
I wish it were easier to get territory specific numbers on individual stackers.
@k00b, would it be hard to do that?