Resolve "Share Kanban view publicly"
This merge request introduces the ability to possibility to share a Kanban view publicly. It also alters the fetching and enhancing of multiple views to avoid N amount of queries.
It's not 100% finished because I took a shortcut in backend/tests/baserow/contrib/database/ws/public/conftest.py
. Here I've excluded kanban views to be included in the tests because it would fail. We need to split the code properly between the baserow and premium folders. I haven't looked into how this should could be done best, I'm open to suggestions. The rest is all finished and can be reviewed.
How to test
- It should be possible to publicly share the Kanban view.
- Password protection should work.
- The publicly shared view should be accessible without JWT token and without providing password if no password is set.
- The publicly shared view should be accessible via the JWT and without proving a password if a password is set.
- The publicly shared view should be accessible without JWT token and without providing a password if a password is set.
- Filtering should work.
- Real time updates should work.
- Only visible fields and their cell values should be exposed.
- If a single select field is chosen for the Kanban view, that one should also be exposed even if it's hidden.
- If a card cover field is chosen for the Kanban view, that one should also be exposed even if it's hidden.
TODO
-
Properly test the kanban
view using thepublic_realtime_view_tester
. Currently it's ignored. I have created an issue for this task: https://gitlab.com/bramw/baserow/-/issues/1211.
Merge Request Checklist
-
changelog.md has been updated if required -
New/updated Premium features are separated correctly in the premium folder -
The latest Chrome and Firefox have been used to test any new frontend features -
Documentation has been updated -
Quality Standards are met -
Performance: tables are still fast with 100k+ rows, 100+ field tables -
The redoc API pages have been updated for any REST API changes -
Our custom API docs are updated for changes to endpoints accessed via api tokens -
The UI/UX has been updated following UI Style Guide
Closes #1146 (closed)
Edited by Bram Wiepjes