be837515fe
1. Add surrounding messages to the given messages so we have a full screen of content to make it feel lively even in quiet rooms
- As you scroll around the timeline across different days, the date changes in the URL, calendar, etc
2. Add summary item to the bottom of the timeline that explains if we couldn't find any messages in the specific day requested
- Also allows you to the jump to the next activity in the room. Adds `/:roomId/jump?ts=xxx&dir=[f|b]` to facilitate this.
- Part of https://github.com/matrix-org/matrix-public-archive/issues/46
3. Add developer options modal which is linked from the bottom of the right-panel
- Adds an option so you can debug the `IntersectionObserver` and how it's selecting the active day from the top-edge of the scroll viewport.
- In the future, this will also include a nice little visualization of the backend timing traces
|
||
|---|---|---|
| .. | ||
| dockerfiles | ||
| fixtures | ||
| .eslintrc.json | ||
| README.md | ||
| client-utils.js | ||
| docker-compose.yml | ||
| e2e-tests.js | ||
README.md
Testing
Setup
If you haven't setup matrix-public-archive yet, see the Setup section in the root README.md
Sorry, this isn't automated yet when you run the tests 🙇
$ docker pull matrixdotorg/synapse:latest
$ docker build -t matrix-public-archive-test-homeserver -f test/dockerfiles/Synapse.Dockerfile test/dockerfiles/
$ docker-compose --project-name matrix_public_archive_test -f test/docker-compose.yml up -d --no-recreate
Running the tests
$ npm run test
Or if you want to keep matrix-public-archive server running after the tests run and explore the output from the interactive URL's printed on the screen, use:
$ npm run test-interactive
Developer utility
$ docker ps --all | grep test_hs
$ docker logs -f --tail 10 matrix_public_archive_test_hs1_1
$ docker logs -f --tail 10 matrix_public_archive_test_hs2_1
$ docker stop matrix_public_archive_test_hs1_1 matrix_public_archive_test_hs2_1
$ docker rm matrix_public_archive_test_hs1_1 matrix_public_archive_test_hs2_1