kalle-app / kalle Goto Github PK

Prisma has support for enums, which we should make use of once we're using a database that supports it.

Passwords never should be saved in cleartext. But as we can not use a token for caldav auth and need to be able to access his calendar we neet to somehow save his password in out DB. To do this we should at least use some form of encrpytion, even though this isn't a really safe way this should ensure that during development we dont accidentally leak passwords.

Replace all Tailwind powered styling by Bootstrap components and individual styles. In addition improve the general UI in terms of design and responsivity.

Is your feature request related to a problem? Please describe.
In Order to make our code better maintainable we should add a Documentation of the code

We need to store the caldav credentials to access a users calendar and get its events.

In the future, we can expand our CI/CD workflow by integrating CD to Heroku (or a comparable provider).
This makes it possible, to always have a working live demo linked to our domain kalle.app which would be really nice for presentations or as showcase.

Describe the bug
An error user.email is null is thrown if navbar is rendered

To Reproduce
open homescreen

Just as CalDav, offer an option to connect Kalle with a Google Calendar / multiple Google Calendars.

A Customer wants to be able to save is common schedule on the Settings page.
Then when creating a new Meeting, he should be able to select this preset or create a custom schedule for the meeting.

So this issue need changes on Settings page for creating a preset and then in the meeting-creation page, to select a preset or instead use a custom schedule.

Is your feature request related to a problem? Please describe.
When selecting an appointment all of the users calendars should be used for this.

At the moment, our auth detection prefers Digest auth. We should prefer basic auth instead, since it's less resource-intensive.

Describe the bug
Edge cases (e.g. meeting not available, no calender connected) currently cause crashes

To Reproduce

1. Register but do NOT connect a calender
2. Create a meeting
3. Access the schedule link

Expected behavior
Show me a notice that this link is not longer valid.

Desktop (please complete the following information):

• all OS and browser

Is your feature request related to a problem? Please describe.
On creating a new meeting a user want to directly have the invitelink copied to his clipboard

Cypress seems like a good E2E testing solution.
There's a Blitz x Cypress recipe that should be useful.

On every PR:

• Run unit tests
• upload coverage reports to Coveralls

I found some code that clearly wasn't run through Prettier in main. It causes big, hard-to-review phantom diffs (as can be seen here). We should make sure that non-Prettier-ised code doesn't make its way into main.

Users might want to switch to a local language and customize E-Mails etc. accordingly.

Is your feature request related to a problem? Please describe.
User wants to be able to define his schedule that he uses often e.g "Normal-working week", "Only mornings"

Describe the solution you'd like
Add a section for setting schedules and be able to select a schedule when creating a new meeting.

Baikal-reliant tests should start the required Docker containers themselves using testcontainers.
This removes the need for running the (clunky) npm run test:baikal:start and :stop.

• default color scheme
• default typography (fonts and h1-6, text etc.
• components with variants
• mobile pages
• desktop pages
• logo

See title.

We should setup a general layout to have a nicer UI until the presentation.

I want to export an existing (open) event (e.g. a online conference) so that everybody can import the event it to their own private calender. I want to send this date in an E-Mail/Newsletter or embed it into a webpage

Is your feature request related to a problem? Please describe.
We currently use the user id for creating a invite-link. This should be replaced to use a username, as it is much more intuitive and nicer to read.

At the moment, it is impossible to book a meeting from 23:00 to 01:00.

I want that to be possible.