| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
(previously tracktrain could end up in a situation where the next and
last station weren't actually adjacent stops, which messed up the
prediction)
|
| |
|
| |
|
| |
|
|
|
|
|
| |
works kinda well, but doesn't complain about unknown config values in
json, which is kinda hmpf tbh
|
|
|
|
| |
most of it deals with timezones, and all the weird implications that has
|
|
|
|
| |
(also some database schema changes, for good measure)
|
| |
|
| |
|
|
|
|
| |
still basic, but works pretty well overall
|
|
|
|
| |
aka use something meant for webapps to write the webapp
|
| |
|
| |
|
|
|
|
| |
(it can do useful stuff! but it also still breaks on some things!)
|
| |
|
|
|
|
|
|
| |
tbh i've kinda lost track at what has all been changed in this, but the
control room form handling now works, and i can write announcements into
the database. Now on to making it do useful things!
|
|
|
|
| |
this does some GHC generics witchery, now in its own module!
|
|
|
|
|
|
| |
just causes pain and isn't really useful for anything since it's a
webform API meant to be used by the web frontend, not by other
applications.
|
|
|
|
|
| |
this automatically derives lucid html versions of ADTs which are
hopefully compatible with the FormUrlEncoded type class
|
| |
|
| |
|
| |
|
|
|
|
| |
(tough mostly untested)
|
| |
|
| |
|
|
|
|
|
|
| |
(or at least something that looks like it might be correct — though
it carries very little information, and lacks things like what the next
stop along the route is)
|
|
|
|
| |
(kinda barebones, but the important things should be there)
|
|
|
|
|
|
|
|
| |
this adds a package for protobuf stuff, generated via hprotoc. Seems to
work kinda fine?
(the generated API is horrible though, will have to write some wrappers
for that)
|
|
|
|
| |
(mostly to make debugging easier, but also more generially useful i guess)
|
|
|
|
|
| |
unfortunately, this makes some responses pretty large. Let's see if it
works this way or if i have to find some way to break them up instead.
|
|
|
|
|
| |
might eventually be needed; until then they're just scaffolding so I
don't loose sight of things
|
|
|
|
|
|
| |
(and they can be useful, too!)
Also, documentation & deleting imports / extensions that aren't used.
|
|
|
|
|
|
| |
(at least for a few simple things)
Also, more modules!
|
|
|
|
|
| |
this doesn't yet actually use the database, but it's getting close to
3am and I should probably go to bed or something
|
|
|
|
| |
lots of lenses in this stuff :(
|
|
|
|
|
|
|
| |
unfortunately doesn't quite get rid of all the type family still
since it's just too useful … but does reduce it somewhat.
Also, maps are much easier for looking things up than vectors!
|
|
|
|
| |
(template haskell doesn't work well with type families, unfortunately)
|
|
|