almanack VS exposure-notifications-server

You need to add the base template to the ParseFS call. The code here is more complicated than it needs to be. You don’t need to go through the FS yourself. The template parser can do that for you. Look at this example which doesn’t use a base template but could: https://github.com/spotlightpa/almanack/blob/master/layouts/layouts.go You would just change it to

For me, GetBooks is a method on a query object and a query object has a DBTX interface struct field. So if I don’t need a transaction, I just use the normal DB as the DBTX but if I do, I call a method to open a TX first and use that. https://github.com/spotlightpa/almanack/blob/master/internal/db/db.go

Pagination is just an offset and a limit. There’s another package that handles the math for you: https://github.com/spotlightpa/almanack/blob/master/internal/paginate/paginate.go

You can have methods on the SQLC structs. They just need to be in a separate file. See https://github.com/spotlightpa/almanack/blob/master/internal/db/page.go eg.

So far, just refactoring. I made a concurrency manager to simplify some stuff, and unified some pagination code. It’s like we said before generics: there are places you miss it, but not having it was never a total blocker. I think going working the x/slices x/maps packages will be the biggest time savers.

I ended up shipping this as a similar autocomplete field: https://github.com/spotlightpa/almanack/blob/master/src/comp...

It's a little different because I put the chosen selections on a row above the input row, but the principle is the same.

https://github.com/spotlightpa/almanack/blob/master/internal/herokuapi/herokuapi_test.go#L14:L21

I’m using Chi not Gorilla, but you can see my JWT Auth middleware here: https://github.com/spotlightpa/almanack/blob/master/pkg/api/routes.go#L37

Not a small one, but a real-life one, the exposure-notifications-server is usually what I like to recommend, keep in mind that you probably need a bit of Go knowledge and context before looking at it so perhaps it isn't the best introductory project to look at; however I recommend you to bookmark it for future reference.

Here, I can even link you to an article of how exposure notifications work: https://www.google.com/covid19/exposurenotifications/

Google's Exposure Notification Reference Serve is a real life example of what you're asking for.

Which is just a massive misunderstanding of how the contact tracing API works, even if you do believe that it was "surreptitiously installed ... on users [sic] phones".

https://www.google.com/covid19/exposurenotifications/ (“The Exposure Notifications System was introduced in an update to Google Play Services. This update did not automatically turn on Exposure Notifications or enable any Exposure Notifications functionality. Exposure Notifications only works if you decide to opt-in.”) Android 6.0 and above.

Source: https://www.google.com/covid19/exposurenotifications/