Read the extension's schema and page the dashboard instead of capping it by EnesYilmazcode · Pull Request #2 · EnesYilmazcode/proscan-web

Vendor the extension's cloud schema and check it stays identical

EnesYilmazcode

committed

7491237

Type runs and pages from the shared schema

EnesYilmazcode

committed

19043bc

Check every document the dashboard reads against the schema

EnesYilmazcode

committed

8230352

Build the rules tests' seed products from the shared schema

EnesYilmazcode

committed

0985ddb

Check every Firestore write against the shared schema, and test sync with the extension's own module

EnesYilmazcode

committed

7088c9e

Keep the audit's adversarial rules probes as a permanent test

EnesYilmazcode

committed

399f3c7

Page the product board with cursors and always show the true count

EnesYilmazcode

committed

78b5025

Page the run inbox instead of capping it at 30

EnesYilmazcode

committed

e65682f

Group runs by the local day they ran, as the extension files them

EnesYilmazcode

committed

bfb523c

Export the whole scope a page at a time, not just the loaded rows

EnesYilmazcode

committed

1b8ee0f

Compare a source's latest two runs page by page

EnesYilmazcode

committed

9aeeecc

Compute deltas and movers per source from its latest two runs

EnesYilmazcode

committed

b8fc830

Drop the composite indexes no query uses

EnesYilmazcode

committed

93dfd37

Keep loading while the only answer is an empty cache

EnesYilmazcode

committed

3612e22

Let Google sign-ins set a password for the extension

EnesYilmazcode

committed

35314de

Ask for 8 characters when creating a password

EnesYilmazcode

committed

50be0ce

Set the password directly when linking says the account's own email is taken

EnesYilmazcode

committed

95a5fc2

Add an e2e run: the extension's sync seeds the emulator, the production bundle is checked

EnesYilmazcode

committed

f9545e7

Run the schema check, unit tests and e2e in CI against the extension's main branch

EnesYilmazcode

committed

8df50a4

Add a dev seed that writes through the extension's sync module

EnesYilmazcode

committed

4202d6f

Document the shared schema, the checks that run the extension, and the e2e

EnesYilmazcode

committed

dc6b38d

Make npm run seed write through the extension, and keep the old fixture as seed:fixture

EnesYilmazcode

committed

cc3f64f

Drop the UTC dayKey helper the run inbox no longer uses

EnesYilmazcode

committed

276ac36

Ignore line endings when comparing the vendored schema

EnesYilmazcode

committed

a1bb939

Keep every loaded page under one live listener, and recount as it changes

EnesYilmazcode

committed

35b2734

Keep check:schema's exit code when the extension checkout is missing

EnesYilmazcode

committed

14a8f73

Serve the favicon in the e2e, and stop its preview server when launch fails

EnesYilmazcode

committed

892865f

Pass deleteField to the extension sync in the e2e seed

EnesYilmazcode

committed

632ca5e

Navigation Menu

Read the extension's schema and page the dashboard instead of capping it - #2

Read the extension's schema and page the dashboard instead of capping it#2
EnesYilmazcode wants to merge 28 commits into
rebuild/p0-sitefrom
rebuild/p4-dashboard

Commits on Sep 24, 2026

Vendor the extension's cloud schema and check it stays identical

Type runs and pages from the shared schema

Check every document the dashboard reads against the schema

Build the rules tests' seed products from the shared schema

Check every Firestore write against the shared schema, and test sync with the extension's own module

Keep the audit's adversarial rules probes as a permanent test

Page the product board with cursors and always show the true count

Page the run inbox instead of capping it at 30

Group runs by the local day they ran, as the extension files them

Export the whole scope a page at a time, not just the loaded rows

Compare a source's latest two runs page by page

Compute deltas and movers per source from its latest two runs

Drop the composite indexes no query uses

Keep loading while the only answer is an empty cache

Let Google sign-ins set a password for the extension

Ask for 8 characters when creating a password

Set the password directly when linking says the account's own email is taken

Add an e2e run: the extension's sync seeds the emulator, the production bundle is checked

Run the schema check, unit tests and e2e in CI against the extension's main branch

Add a dev seed that writes through the extension's sync module

Document the shared schema, the checks that run the extension, and the e2e

Make npm run seed write through the extension, and keep the old fixture as seed:fixture

Drop the UTC dayKey helper the run inbox no longer uses

Ignore line endings when comparing the vendored schema

Keep every loaded page under one live listener, and recount as it changes

Keep check:schema's exit code when the extension checkout is missing

Serve the favicon in the e2e, and stop its preview server when launch fails

Pass deleteField to the extension sync in the e2e seed