This has several advantages over using an external CLI tool to generate
the files, such as having fewer dependencies, less generated files bloat
and more flexibility over the localization code. "Sadly", this solution
doesn't check for validity of JSON files at compile-time (the only
advantage of using an external tool such as go-localize). However, I
easily fixed this huge "issue" by making the program crash at startup if
any locale files are invalid.
Also, no more "go-localize removed from go.mod" "go-localize added to
go.mod" "go-localize removed from go.mod" spam. A utility for making
sure all translation stay in sync soon! (not sure where to put it)
No one really understood what they meant.
Also, please stop removing chekoopa's localizer package from
dependencies. It keeps coming back when I make dev.
GET /login and POST /login-data are merged into /login.
GET /logout and POST /logout-confirm are merged into /logout.
The logout form now looks more consistent with other forms.
Used io.WriteString instead of Fprint where it wasn't like that for some reason.
* There is a link to the hypha in question in the heading, similar to other pages related to a selected hypha.
* The locale keys (?) are reworded to get rid of the word ‘query’.
* The phrasing is more precise. Kinda verbose doe.
This weird hack did that:
* Contained two packages in one folder (main and tools)
* Imported two commands, which is illegal in Go
It seems that the hack ensured that the go generate dependencies were installed. Well, why should that be ensured?
make → make
make run → run
make check → check
It still doesn't track any dependencies to avoid unnecessary rebuilds
(like before), but eh. The Go toolchain does, though.
