5e2bf0bdca
* [chore] Remove years from all license headers Years or year ranges aren't required in license headers. Many projects have removed them in recent years and it avoids a bit of yearly toil. In many cases our copyright claim was also a bit dodgy since we added the 2021-2023 header to files created after 2021 but you can't claim copyright into the past that way. * [chore] Add license header check This ensures a license header is always added to any new file. This avoids maintainers/reviewers needing to remember to check for and ask for it in case a contribution doesn't include it. * [chore] Add missing license headers * [chore] Further updates to license header * Use the more common // indentend comment format * Remove the hack we had for the linter now that we use the // format * Add SPDX license identifier |
||
---|---|---|
.. | ||
README.md | ||
account.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 | ||
routersession.go | ||
status.go | ||
statusbookmark.go | ||
statusfave.go | ||
statusmute.go | ||
tag.go | ||
token.go | ||
user.go |
README.md
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!