Initial Backend #3
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mxmeinhold
force-pushed
the
mom/backend-init
branch
from
bc6b292 to
f5876e6
Compare
After a terrible adventure trying to use nicer tools than raw sql to access the db while having very little bandwidth to explore documentation, we're relegated to using raw sql
Need to fill in a lot more data, but this is the basis
Have to assemble clues by their parent child relationships
No support for rules yet
mxmeinhold
force-pushed
the
mom/backend-init
branch
from
f5876e6 to
67cfbef
Compare
|
each request works, maybe we could add checking so names are unique? Not super necessary because the searching could be from tags, but searching by name would make the most sense for a user. |
|
Yeah, we definitely need to add more constraints in the db |
|
I think it’s in a good state for now for Main at least, I will probably make CRUD and like search in a separate branch |
Adding windows db migration commands
WillNilges
approved these changes
Jun 19, 2025
| * Be sure to defer logger.Sync() to ensure it's flushed before we exit | ||
| */ | ||
| func GetLogger(ctx context.Context) *zap.Logger { | ||
| // TODO we should probably handle the error |
| ) | ||
|
|
||
| const ( | ||
| connStr = "postgres://postgres:test@localhost:5432/postgres?sslmode=disable" |
There was a problem hiding this comment.
Why is this hardcoded in the app? Guessing the config will override it but not how I typically do things.
| rw.Write(data) | ||
| }) | ||
|
|
||
| /* |
There was a problem hiding this comment.
Nice comments. Could you do that for the other routes above ☝🏻
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Initial setup for the backend, including db migrations, configuration, logging, tracing, and routes for interacting with cluesheets, clues, and user participation. A great deal is not implemented and a great deal is subject to change, but let's get something into main shall we?