studio/calendars
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

✨(freebusy) add availability management (#35)

Browse Source 
Adds organization-level default calendar sharing controls, "Find a Time" scheduling UI with a Free/Busy timeline showing attendee availability and conflicts, Working hours editor in Settings to manage and save availability, Autocomplete attendee search with debounced, partial name/email matching and timezone display.

Fixes #26. Fixes #25. Fixes #24.
This commit is contained in:
Sylvain Zimmer
2026-03-10 01:30:42 +01:00
committed by GitHub
parent 9c18f96090
commit 7cb8d5e7b6
49 changed files with 3714 additions and 246 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@@ -82,12 +82,20 @@ Your Docker services should now be up and running! 🎉
You can access the project by going to <http://localhost:8930>.
You will be prompted to log in. The default credentials are:
You will be prompted to log in. The following test users are
pre-configured in Keycloak (password = username prefix):
```
username: calendars
password: calendars
```
| Email | Password | Org domain |
|---|---|---|
| `user1@example.local` | `user1` | `example.local` |
| `user2@example.local` | `user2` | `example.local` |
| `user3@example.local` | `user3` | `example.local` |
| `user1.2@example2.local` | `user1.2` | `example2.local` |
| `user2.2@example2.local` | `user2.2` | `example2.local` |
Users sharing the same domain are placed in the same organization
automatically on first login. Use users from different domains
(`example.local` vs `example2.local`) to test cross-org isolation.
Note that if you need to run them afterward, you can use the eponym Make rule: