isMultiCalendar
as true
. This allows your application to handle multiple Google calendar accounts seamlessly, providing a more flexible experience for users who manage several calendars.
Below code snippet can be used to render the Google calendar connect button for multiple users
Name | Required | Description |
---|---|---|
className | No | To pass in custom classnames from outside for styling the atom |
label | No | The label for the connect button |
alreadyConnectedLabel | No | Label to display when atom is in already connected state |
loadingLabel | No | Label to display when atom is in loading state |
onCheckError | No | A callback function to handle errors when checking the connection status |
redir | No | A custom redirect URL link where the user gets redirected after successful authentication |
initialData | No | Initial data to be passed |
isMultiCalendar | No | Specifies if the button supports integration for multiple users |
tooltip | No | In case user wants to pass external tooltip component |
tooltipSide | No | Specifies what direction the tooltip appears |
isClickable | No | Boolean to disable button or not |
onSuccess | No | A callback function to handle success when checking the connection status |
Please ensure all custom classnames are valid Tailwind CSS classnames. Note that sometimes the custom
classnames may fail to override the styling with the classnames that you might have passed via props. That
is because the clsx utility function that we use to override classnames inside our components has some
limitations. A simple get around to solve this issue is to just prefix your classnames with ! property just
before passing in any classname.