Skip to content

Add concept overview for Google suite hub#1

Open
mattiluki wants to merge 2 commits into
mainfrom
codex/develop-4-in-1-google-app
Open

Add concept overview for Google suite hub#1
mattiluki wants to merge 2 commits into
mainfrom
codex/develop-4-in-1-google-app

Conversation

@mattiluki
Copy link
Copy Markdown
Owner

Summary

  • add README describing the planned 4-in-1 dashboard for Gmail, Tasks, Calendar, and Habits
  • outline OAuth setup, API scopes, and backend flow requirements
  • include checklist and data model notes for future implementation

Testing

  • not run (documentation-only changes)

Codex Task

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread README.md
Comment on lines +31 to +35
1. Redirect the user to Google's OAuth URL with scopes:
- `https://www.googleapis.com/auth/gmail.readonly`
- `https://www.googleapis.com/auth/tasks.readonly`
- `https://www.googleapis.com/auth/calendar.readonly`
2. Exchange the authorization code for access + refresh tokens.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Request offline consent before expecting refresh tokens

The minimal OAuth flow instructs calling Google’s authorization URL with only the three API scopes (lines 31‑34) yet step 2 assumes the code exchange will yield refresh tokens. For Google web apps, a refresh token is only issued when the initial authorize request includes offline consent parameters (e.g., access_type=offline and, after first grant, prompt=consent); otherwise you only receive a short‑lived access token and the later persistence/refresh logic cannot work. Please add the offline consent flags to the authorize step so refresh tokens are reliably returned.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant