api: header and parameter names.

[thruflo]

This is a rebase of some changes to rename:

• electric-chunk-last-offset -> electric-offset
• electric-next-cursor -> electric-cursor
• electric-shape-handle -> electric-handle
• ?shape_handle -> ?handle

Painfully rebased on the previous shape_handle and table path -> query param change in #1798).

So I believe we can merge this instead of those and this will match the new documentation. I haven't yet added a changeset.

[netlify]

✅ Deploy Preview for electric-next ready!

Name	Link
🔨 Latest commit	8261b25
🔍 Latest deploy log	https://app.netlify.com/sites/electric-next/deploys/6723a9346815ef00084adac4
😎 Deploy Preview	https://deploy-preview-1900--electric-next.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[thruflo]

Btw, I don't understand why the typecheck tests are failing. pnpm typecheck runs fine for me locally in both the react-hooks and typescript-client packages:

➜  react-hooks git:(thruflo/header-naming) ✗ pnpm run typecheck

> @electric-sql/react@0.4.7 typecheck /Users/thruflo/Development/electric-sql/electric/packages/react-hooks
> tsc -p tsconfig.json

➜  react-hooks git:(thruflo/header-naming) ✗ cd ..
➜  packages git:(thruflo/header-naming) ✗ cd typescript-client
➜  typescript-client git:(thruflo/header-naming) ✗ pnpm run typecheck

> @electric-sql/client@0.6.5 typecheck /Users/thruflo/Development/electric-sql/electric/packages/typescript-client
> tsc -p tsconfig.json

[msfstef]

@thruflo the react-hooks package depends on the typescript client, so you need to first pnpm build the typescript client and then run pnpm typecheck on the react hooks package

[thruflo]

Yup, I've pnpm -r builded from the repo root locally.

I'm not really the right person to revise the way we run our CI tests :)

[msfstef]

@thruflo I was also seeing the same issue - typecheck passed locally but failed on CI, and the lines referenced on CI for the errors did not match the actual test file, so something odd happening there...

There's a conflict now so tests aren't running though.

[thruflo]

@msfstef fixed the conflict.

[msfstef]

@thruflo types fixed 💪 🚀