You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
StatusIds, NotificationIds and AccountIds are using a default show instance to render to the API. This means that all GET calls for notifications will not be able to use the "in_reply_to_id" or the "since_id" features.
These probably require a unique instance in their argument type. I've been patching it with instances like this:
instanceShowStatusIdwhereshow= unStatusId
However, this is really not the best option as it makes debugging worse.
The text was updated successfully, but these errors were encountered:
KirinDave
added a commit
to KirinDave/hastodon
that referenced
this issue
Jun 20, 2019
StatusIds, NotificationIds and AccountIds are using a default show instance to render to the API. This means that all GET calls for notifications will not be able to use the "in_reply_to_id" or the "since_id" features.
These probably require a unique instance in their argument type. I've been patching it with instances like this:
However, this is really not the best option as it makes debugging worse.
The text was updated successfully, but these errors were encountered: