nextlove
nextlove copied to clipboard
seamapi
An NPM module that has best practices and essential modules for building APIs with NextJS
Could be converted from OpenAPI generation The OpenAPI conversion has a little jank in my experience (auth gets set to `seam-workspace` as a header for all endpoints). Maybe there's something...
Currently I think for arrays in query parameters, the logic erroneously assumes the contents are a string, and does not validate them
See error (collapsed) below. Confirmed in this PR https://github.com/seamapi/fake-seam-connect/pull/32 Details ``` > tsup CLI Building entry: src/index.ts CLI Using tsconfig: tsconfig.build.json CLI tsup v7.1.0 CLI Using tsup config: /home/runner/work/fake-template/fake-template/tsup.config.ts CLI...
In relation to: https://github.com/seamapi/nextlove/pull/82 The PR is too big and dangerous as is. This issue is to design an approach for getting edge-support merged First let's get some opinions out...
- edge initial commit - edge stuffs - poc ready - mirroring the interface - no need to have two wrappers if the interface is mirrored
This PR contains a LOT of stuff, and will probably be split into some PRs 1. edge only supports web native API, so some things we do in the generated...
``` 5:18 error Don't use `{}` as a type. `{}` actually means "any non-nullish value". - If you want a type meaning "any object", you probably want `Record` instead. -...