-
v0.3.1 protectedb2a066fb · ·
- origin/main fix src/api dependency to window (breaking tests), defaults to https - fix test user search results - cleanup tests env vars - fix matrix-room-state display of chilrend rooms - feat/uhtml matrix-room use dom getter helpers for dom manipulation - use fieldset(s) for matrix-create-room - fix matrix-event example and when no data - update dev docs for local homeserver - rm docker-compose - rm docker-compose, local homeserver uses matrix synapase docker - fix homeserver/readme.md - update homeserver/readme - fix website build (include dompurify) - improve login,logout,register examples - cleanup login,logout markup - fix auth-stage[base-url] for register - fix matrix-register-username-available[base-url] in register - fix register - fix matrix-room example - log mwc on home - add api.{getAccountData,setAccountData} - do not minifiy website's code - fix index.html favicon - improve examples/matrix-room-context/index.html attrs & data loading - fix examples/matrix-room-context/index.html remote URL data loading - improve matrix-room(-context) examples - try fetch data for matrix-room-context example - update matrix-room examples to links generating the URL for the page - add <link rel="icon" href="../../src/svg/logo.svg" /> to examples
-
v0.3.0 protected4eaaf179 · ·
- add docker and docker-compose for a local synapase homeserver config - refactor `api` service initilisation with `baseUrl` - refactor `api` to use `this.baseUrl` for all fetch - allow `login` to discover baseUrl from .well-known from the user's homeserver (also http localhost) - `registerUserKind` accepts `baseUrl` as second argument # missing - tests & CI should use local temporary homeserver
-
v0.2.6 protectedc0979246 · ·
- matrix-send-event(s)[is-widget] will not call the API, but still send the `mxevent` DOM event, so they can be used in widgets - room state events use the events-manager service, for form (display not displayed yet; `matrix-state-event` tbd) - refactor exports for `/templates/matrix-event/`, ready to be used in the events-manager - matrix-send-event(s), with the events-manager will discover state events from the sepc `m.<event_type>` (or custom events can be set with a boolean when registered)
-
v0.2.5 protected1d356702 · ·
Improve `matrix-search` behavior, attribute APIs, docs: - `apisearch` will allow calling /search on the homeserver (via `mwc.api.search(matrixSpecSearchBody)`, like before) - `quicksearch` will load the joined rooms as HTML datalist to the input (be can be used in conjunction or independent` - `quicksearch-events` will load the events from attribute as JSON stringyfied Array of MatrixEvent(s) - Fix the bug of datalist ID being "not unique" in the DOM (therefore also not in JS window/document, and being shared across instances of matrix-search; not what we wanted) - add `legend` and `placeholder` attributes for customizing what is shown on the screen
-
v0.2.4 protected313de144 · ·
- fix error; remove unecessary room name access in api room info - add `mwc.api.search()` to search events in joined rooms on the `/search` matrix homeserver endpoint - add `matrix-search` web-component to display a basic UI for the search endpoint - refactor `mwc.api.checkMatrixId()` so the function is clearer and provides better match (for matrix-event.onInput → checkMatrixId → `libli.org,matrix.to,matrix.actor)/<matrix_id>`) - fix ci (local works) for vite.build.external = ["dompurify"] - import DOMPurify (from npm) only on room example page (peer deps) ← should do that on every page where we want matrix-room[flag-sanitizer="true"] to work (peer deps from mwc) - put roomStateEventsToRoomInfo out of service/api for clarity (gotta refactor to following the "matrix answer" better, array of event; by their types?) - start refactor all dom events `mx*` sent by mwc components, into services/dom-events.js of 'types' like structure; to be continue with "non standard" ("auth" etc.), and maybe use `io.gitlab.sctlib.mwc.<event_name>` to follow convention (and what is started in libli?)
-
v0.2.2 protectedef8f214d · ·
- [BREAKING] move `eventsManager` from `mwc.api.eventsManager` to `mwc.eventsManager` - re-organize folder structure, to clear root folder, and move "services" (api etc.) under `src/services` - fix and use tests - create matrix-error - improve matrix-login,logout,auth - [BREAKING] renamed `matrix-auth` slots - improve docs and examples
-
v0.2.1 protected2c97764c · ·
- `matrix-event` now uses `displayTemplate` (similar to previous `formTemplate`) to display an event's content by its type, using a custom web-component (user defined) - `matrix-event` > `matrix-event-content` → inserts the content of the `displayTemplate` and assign the `event=""` attribute on the first children HTML (JSON stringify) - use the folder `src/template/:matrix.event.type/{form,display}.js` for modular registration of each of an "event's components" (display and form) - create `matrix-event-room-message` for default `m.room.message` event type, and example of other types
-
v0.2.0 protected1f46d105 · ·
Breaking changes (see docs and examples for each components): - matrix-send-event has a new API - api.eventsManager(name, {formTemplate, displayTemplate}) to register custom events (only form to send now; coming display and edit) - matrix-send-events to offer custom multi events type sending - matrix-room[show-send-event,send-event-types] should work as before with the new API, but the <slot name="send"> children have changed - removes the indexedDB in favor of previous localstorage, because indexedDB introduced async, and we did not handle that correctly
-
v0.1.10 protectedfb38a509 · ·
(might need to cleanup the page local storage / indexed db & login again) - display room avatar from `mxc` URI to matrix media thumbnail URL - refactor `api.mxcUriToUrl` for thumbnail and download links - refactor images/thumbnails/files/media URL over components - remove `homeserver` attribute reference/requirement on most components - remove `homeserver` requirement for media api function calls (only `mxc` URI is required, the `homeserver` is stored inside) - store auth in indexedDB - add service worker to intercept api calls (future cache + offline first) - add broadcast channel for service worker to page communication