oxalica 73eb441a26 refactor(*): use term msg to replace item ... - `Msg` or `msg` is now the canonical term for the substructure in a room. It includes a `chat` subtype and (in the future) other administration subtypes like member joining or leaving. - `Message` or `message` can used in human oriented context like docs and comments, but only when it is unambiguous. - `message` is not chosen in code because it's hard to type (at least for me!), and have ambiguous meaning of: - "Human readable text" in context of `ApiError`'s field. - "A unit of data transfer, datagram" in context of WebSocket Message. - `item` is not chosen because it is overly generic.		2024-09-13 03:32:11 -04:00
..
index.html	refactor: reorganize docs and aux files	2024-09-10 03:59:31 -04:00
webapi.yaml	refactor(*): use term msg to replace item	2024-09-13 03:32:11 -04:00