screen-capture.webm
Deployed at convin.pythonanywhere.com
-
I have followed the git rebase oriented workflow.
-
Each commit has been created with a meaningful commit message.
-
Helper functions are used instead of putting everything inside views. DRY
-
Only Google's provided standard libraries are used.
-
URL configurations keeping extensiblity (v2, v3) in mind.
-
Exception handling with appropriate status codes.
-
rest/v1/calendar/init
returns the auth_url.
now depending on the client e.g. mobile, desktop, etc. we can open (prompt) the url in a new browser tab.
-
rest/v1/calendar/redirect
serves as a redirect URI.
It fetches auth_code and then exchanges the code for 'access_token' and 'refresh_token' from the google' server.
-
We can use any client to access the api endpoints
-
If the status of our app is set to Production (i.e. everyone can use it)
- Then our app needs verification from Google to use the scope (which is not possible in 48 hours)
-
Currently the status of our app is set to Testing
- A whitelisted set of users can use the scope without verfification (Which is our case)
-
Hence, If you want to test this via convin.pythonanywhere.com
- Login using this Google account (I have whitelisted this as test user)
- Account: [email protected] , Password: TestAccount@1144
-
Another option is to setting this up locally and configuring your own
client_secret.json
and test users.