summaryrefslogtreecommitdiff
path: root/internal/api/model/status.go
diff options
context:
space:
mode:
authorLibravatar tobi <31960611+tsmethurst@users.noreply.github.com>2022-05-28 19:59:55 +0200
committerLibravatar GitHub <noreply@github.com>2022-05-28 18:59:55 +0100
commitae5402ada6aa794a69de455f745934b27e030d3d (patch)
tree93d228443da821b0b38cc1417742e65e92e5edec /internal/api/model/status.go
parent[frontend] Reduce width of profile img with screen width (#615) (diff)
downloadgotosocial-ae5402ada6aa794a69de455f745934b27e030d3d.tar.xz
[chore] Mastodon api fixups (#617)
* don't omitempty on description * don't omitempty on any fields * add ms to timestamp format * don't omitempty on text_url * rearrange attachment fields a bit * just give URL again as attachment text url * update tests * fix accidental replace
Diffstat (limited to 'internal/api/model/status.go')
-rw-r--r--internal/api/model/status.go8
1 files changed, 4 insertions, 4 deletions
diff --git a/internal/api/model/status.go b/internal/api/model/status.go
index fade58a49..6e25f787a 100644
--- a/internal/api/model/status.go
+++ b/internal/api/model/status.go
@@ -30,10 +30,10 @@ type Status struct {
CreatedAt string `json:"created_at"`
// ID of the status being replied to.
// example: 01FBVD42CQ3ZEEVMW180SBX03B
- InReplyToID string `json:"in_reply_to_id,omitempty"`
+ InReplyToID string `json:"in_reply_to_id"`
// ID of the account being replied to.
// example: 01FBVD42CQ3ZEEVMW180SBX03B
- InReplyToAccountID string `json:"in_reply_to_account_id,omitempty"`
+ InReplyToAccountID string `json:"in_reply_to_account_id"`
// Status contains sensitive content.
// example: false
Sensitive bool `json:"sensitive"`
@@ -67,13 +67,13 @@ type Status struct {
// This status has been bookmarked by the account viewing it.
Bookmarked bool `json:"bookmarked"`
// This status has been pinned by the account viewing it (only relevant for your own statuses).
- Pinned bool `json:"pinned,omitempty"`
+ Pinned bool `json:"pinned"`
// The content of this status. Should be HTML, but might also be plaintext in some cases.
// example: <p>Hey this is a status!</p>
Content string `json:"content"`
// The status that this status reblogs/boosts.
// nullable: true
- Reblog *StatusReblogged `json:"reblog,omitempty"`
+ Reblog *StatusReblogged `json:"reblog"`
// The application used to post this status, if visible.
Application *Application `json:"application"`
// The account that authored this status.