Daily video calls

[lunchpaillola]

Adding Daily Video Calls to Calendso. Here's a demo of what creating and joining a video room looks like

`https://www.loom.com/share/f1fe710a081a46078621749d532a6e1c```

[vercel]

Someone is attempting to deploy a commit to the cal Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

Someone is attempting to deploy a commit to the cal Team on Vercel.

A member of the Team first needs to authorize it.

[amirhmoradi]

Hi @lunchpaillola , thanks for the great work. I have some feedback if you don't mind :)

I believe we could use already available "isdedicated" concept and avoid hard coding an external provider (ie Daily here) in the event manager (and other places).

For the db side, I would also suggest having a separate table to hold Daily's info and reference the booking id. Core tables shall theoretically be clean of external providers, to allow for better future evolutions.

About migrations, it would be best to have just one migration per PR. You could prepare it by going from a base DB (from latest main branch) and the applying your schema and then generating the migration)

For the emails templates, we could condition the meeting username and password existence and so avoid the hard coded provider condition.

Also, I would suggest having another PR for code indentation fixes and lib/deps updates.

I would love to see your PR merged soon :)

[lunchpaillola]

Hi @lunchpaillola , thanks for the great work. I have some feedback if you don't mind :)

I believe we could use already available "isdedicated" concept and avoid hard coding an external provider (ie Daily here) in the event manager (and other places).

For the db side, I would also suggest having a separate table to hold Daily's info and reference the booking id. Core tables shall theoretically be clean of external providers, to allow for better future evolutions.

About migrations, it would be best to have just one migration per PR. You could prepare it by going from a base DB (from latest main branch) and the applying your schema and then generating the migration)

For the emails templates, we could condition the meeting username and password existence and so avoid the hard coded provider condition.

Also, I would suggest having another PR for code indentation fixes and lib/deps updates.

I would love to see your PR merged soon :)

Thanks for your review and the comments!

[baileypumfleet]

Code looks good to me, will do some local testing now.

[zomars]

This is awesome! @lunchpaillola

Would you kindly add instructions on how to setup the integration like the other ones in the README.md?

EDIT: I've stumbled upon this error when trying to test it locally:

EDIT 2: Also, can we type cast this so we know what properties to expect from the response?