gotosocial/internal/gtsmodel
Daenney c1375ca5c1
[chore] Remove go-playground/validator (#2069)
* [chore] Remove go-playground/validator

It turns out we're not actually using the validator code. This is a
remnant from when we intended to use it, but the presence of it and its
struct tags creates the illusion we're validating a lot of things we're
not. It resulted in some confusion when we were trying to figure out
language valdiation.

Remove all this code, so that only the validation functions from the
validate package we actually use remain. I'm not touching the struct
tags in the migrations in order to avoid things potentially thinking
migrations need to be re-run.

* [chore] Bring back a struct tag on api

The validate on internal/api is Gin doing form validation, not the
validator from go-playground/validator.
2023-08-06 12:22:40 +02:00
..
account.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
accountnote.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
admin.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
application.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
block.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
client.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
domainblock.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
emaildomainblock.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
emoji.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
emojicategory.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
follow.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
followrequest.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
instance.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
list.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
marker.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
mediaattachment.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
mention.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
notification.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
README.md Prune unnecessary nullzeros, fixup db tags (#200) 2021-09-10 10:08:21 +02:00
report.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
routersession.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
status.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
statusbookmark.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
statusfave.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
statusmute.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
tag.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
token.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
tombstone.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00
user.go [chore] Remove go-playground/validator (#2069) 2023-08-06 12:22:40 +02:00

A note on when we should set data structures linked to objects in the database to use the bun nullzero tag -- this should only be done if the member type is a pointer, or if the this primitive type is literally invalid with an empty value (e.g. media IDs which when empty signifies a null database value, compared to say an account note which when empty could mean either an empty note OR null database value).

Obviously it is a little more complex than this in practice, but keep it in mind!