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
The backend now provides a /api/v1/messages/ endpoint that returns by default the 10 latest messages stored. We should present these somewhere on the home page when a user is logged in.
To finish this we need:
A new API route that fetches messages
A new component that use useSWRImmutable to fetch some messages and then presents them in a decent format, probably a table.
When presenting the messages, we should present the text and is_assistant fields. The client side should retain the id and parent_id for later features.
The text was updated successfully, but these errors were encountered:
I think we can treat them separately. This is more structured as a news feed of messages that have been submitted globally. I expect the messages in this feed would be unrelated to each other.
Visually they could share the same components but I think it's also sensible for them to have distinct styles since their purposes diverge.
The backend now provides a
/api/v1/messages/
endpoint that returns by default the 10 latest messages stored. We should present these somewhere on the home page when a user is logged in.To finish this we need:
useSWRImmutable
to fetch some messages and then presents them in a decent format, probably a table.When presenting the messages, we should present the
text
andis_assistant
fields. The client side should retain theid
andparent_id
for later features.The text was updated successfully, but these errors were encountered: