Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

GS: Google OAuth, Picker, and snapshot export

Open
#399 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
google-cloud, typescript

Research direction

Start with docs/design/google-sheets/authentication.md, docs/design/google-sheets/snapshot-export.md, and docs/design/google-sheets/large-results.md, then locate the existing streaming and type-conversion entry points. Done means the gated OAuth, Picker selection, and one-time export satisfy the listed security, upload, error-handling, and unit, fake-Google, browser, and scale-test criteria.

Written by the indexing model from the issue text.

Description

cool feature

Parent: #398

Design:

  • docs/design/google-sheets/authentication.md
  • docs/design/google-sheets/snapshot-export.md
  • docs/design/google-sheets/large-results.md

Scope

Add deployment-gated Google Identity Services authentication, Google Picker create/select flow, and one-time snapshot export using the canonical streaming/type-conversion pipeline.

Acceptance criteria

  • Google actions are absent when configuration is missing.
  • Tokens remain in browser memory and never enter URLs, logs, persistence, or exports.
  • New and existing spreadsheets can be selected with edit-permission validation.
  • Snapshot export creates no binding, refresh link, checkpoint, or history row.
  • Values use RAW input semantics and precision-safe ClickHouse type mapping.
  • Upload uses explicit byte-bounded ranges with progress, cancellation, quota backoff, and no silent truncation.
  • OAuth popup/account/permission failures are actionable and non-destructive.
  • Unit, fake-Google, browser, and scale tests cover the flow.

Non-goals

Linked refresh, server binding storage, scheduling, Apps Script, service accounts, and Google Docs.

Dominant language
TypeScript
Stars
8
Forks
2
Avg merge
1h 34m
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Altinity/altinity-sql-browser

All issues in Altinity/altinity-sql-browser

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.