| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Make the responses for various data creation requests more consistent. | Owen Jacobson | 2024-10-19 |
| | | | | | | | | | | | | | | | | | | | | | In general: * If the client can only assume the response is immediately valid (mostly, login creation, where the client cannot monitor the event stream), then 200 Okay, with data describing the server's view of the request. * If the client can monitor for completion by watching the event stream, then 202 Accepted, with data describing the server's view of the request. This comes on the heels of a comment I made on Discord: > hrm > > creating a login: 204 No Content, no body > sending a message: 202 Accepted, no body > creating a channel: 200 Okay, has a body > > past me, what were you on There wasn't any principled reason for this inconsistency; it happened as the endpoints were written at different times and with different states of mind. | ||
| * | Get loaded data using `export let data`, instead of fishing around in $page. | Owen Jacobson | 2024-10-17 |
| | | | | | | | This is mostly a how-to-Svelte thing. I've also made the API responses for invites a bit more caller-friendly by flattening them and adding the ID field into them. The ID is redundant (the client knows it because the client has the invitation URL), but it makes presenting invitations and actioning them a bit easier. | ||
| * | Organizational pass on endpoints and routes. | Owen Jacobson | 2024-10-16 |
| | | |||
| * | Return a distinct error when an invite username is in use. | Owen Jacobson | 2024-10-11 |
| | | | | | I've also aligned channel creation with this (it's 409 Conflict). To make server setup more distinct, it now returns 503 Service Unavailable if setup has not been completed. | ||
| * | Create APIs for inviting users. | Owen Jacobson | 2024-10-11 |
 |
index : pilcrow | |
| Run-It-Yourself web chat, maybe |
| summaryrefslogtreecommitdiff |