forked from mirrors/gotosocial
b42469e4e0
* add custom css account property + db func to fetch * allow account to get/set custom css * serve custom css for an account * go fmt * use monospace for customcss, add link * add custom css to account cache * fix broken field * add custom css docs to user guide * add `accounts-allow-custom-css` config flag * add allow custom css to /api/v1/instance response * only show/set custom css if allowed to do so * only set/serve custom account css if enabled * update swagger docs * chain promise * make bool a bit clearer * use cache for GetAccountCustomCSSByUsername |
||
|---|---|---|
| .. | ||
| account.go | ||
| admin.go | ||
| application.go | ||
| block.go | ||
| client.go | ||
| domainblock.go | ||
| emaildomainblock.go | ||
| emoji.go | ||
| follow.go | ||
| followrequest.go | ||
| instance.go | ||
| mediaattachment.go | ||
| mention.go | ||
| notification.go | ||
| README.md | ||
| routersession.go | ||
| status.go | ||
| statusbookmark.go | ||
| statusfave.go | ||
| statusmute.go | ||
| tag.go | ||
| token.go | ||
| user.go | ||
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!