-
Notifications
You must be signed in to change notification settings - Fork 33
[$75] Missing fields of connected calendars #590
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Assigned to @mahidulalvi-bonic |
Fix issues for 'missing fields of connected calendars' #590.
@mahidulalvi-bonic paid via https://www.topcoder.com/challenges/e4c8b4b9-aa38-4a68-89fa-4fad61f3f7f7 |
@maxceem I am currently able to view only 4 fields and accessToken field is missing and accountId field is displayed as email |
@sandhiyakavi that's an expected behaviour. I think we can treat this issue as internal technical issue, if scheduling/calendar connection work well, it means that we get all the necessary fields.
|
Unable to verify this in production since we haven't released connect calender feature to production yet. |
Branch:
feature/interview-update
There are various cases when after adding or deleting calendars, some calendars are missing in the UserMeetingSettings record. Expected behaviour: each calendar should always have the next 5 fields:
id
<- calendar idaccountId
accountProvider
accessToken
isPrimary
Failed Cases
Missing fields:
id
andisPrimary
flag, see screenshotid
andisPrimary
id
for google calendar, see screenshotid
, see screenshotI guess most of these issues are because of the missing
id
.Task
Verify all these cases and make sure that we always have all 5 fields in all calendar records:
is_primary
at Nylas.is_primary
at Nylas.is_primary
at Nylas.is_primary
at Nylas.The text was updated successfully, but these errors were encountered: