overengineeringstudio / overengineeringstudio/effect-utils

notion-react: add live coverage for upload-backed media and column width ratios once API support is proven

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

Nobody has claimed this yet.

origin:agent type:chore type:feature
Dominant language
TypeScript
Stars
82
Forks
2
Avg merge
1d 8h
Merged PRs (30d)
121

Description

Context

  • The public notion-react demo page now covers the current sync-safe surface end to end.
  • Two Storybook surfaces remain intentionally excluded from live public syncs because the Notion API does not currently accept them reliably in our probes.

Gaps

  • upload-backed media blocks (video, audio, file, pdf) reject external URLs on create and need the file_upload pipeline before they can be part of the rerunnable public demo
  • column widthRatio / width_ratio is implemented in the local prop and host-projection surface, but live append probes against Notion still fail

Follow-up

  • add an integration probe or e2e that proves the live API contract for each surface
  • when a stable live path exists, replace the caveat entries on the public demo page with first-class synced examples
  • decide whether width ratios should remain a local-only feature until live API support is available

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start with the notion-react public demo and the two excluded Storybook surfaces; review the current sync-safe examples and local widthRatio/width_ratio projection. Add integration probes or e2e coverage for video, audio, file, pdf, and column ratios, then replace demo caveats only after stable live API support is proven; record whether ratios remain local-only.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, storybook, typescript
Domain
api, frontend, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.