Comments (7)
What prevents you from using that library using npx
? I agree something like that would be a nice feature, but does writing a simple interface per table really take a significant portion of the development time? I can only imagine it does if you are writing a very simple crud.
While something like this would be a nice feature, It's a lot of work to write and maintain it. It would be helpful for people migrating an existing codebase to Kysely though.
Kysely already has the db.introspection module, which could be used to implement this.
from kysely.
To be fair, if sql-ts
really works, code would not have to to be copy pasted. Instead Kysely could include sql-ts
as an optional dependency.
And there is a benefit beyond saving time: automatic generation prevent errors when creating the type interfaces.
from kysely.
Nothing prevents. It was a suggestion!
from kysely.
What I meant was, if that library already does what you need, why not use it to create the interfaces for Kysely? If it works, why would we need to copy paste the code to Kysely?
from kysely.
sql-ts
has a CLI you can run using npx
without installing anything locally.
from kysely.
Yeah, they dont need to depend on each other. They can work in parallel where we simple import the types from the generated sql-ts
file.
import { Person, Pet, Movie } from './sql-ts-generated';
interface Database {
person: Person
pet: Pet
movie: Movie
}
from kysely.
Sure, I was just saying that sql-ts could be integrated without copy and pasting code. If you don't want to go that route, no worries.
from kysely.
Related Issues (20)
- Compile time checks for empty arrays HOT 2
- Incorrect types and missing suggestions when using object index signature HOT 2
- UUID doesn't seem to work for inserts (Postgres) HOT 1
- Loose typechecking on innerJoin/leftJoin comparisons HOT 2
- TypeChecking for doUpdateSet not working since 0.27.0 HOT 3
- Support "using" in joins
- [Q] Reusable CTE (psql) HOT 1
- Issue with parentheses in Postgres using a conflict expression HOT 1
- Query execution result type always resolves to an empty object i.e. "{}" HOT 2
- camelCase plugin is not being applied to subquery results that incorporates jsonArrayFrom HOT 3
- Streaming results not working on Deno for PostgreSQL HOT 2
- Case of extremely slow type checking HOT 4
- ParseJSONResultsPlugin HOT 1
- `INCLUDE` clause in Postgres `createIndex`
- Pass client instance HOT 3
- Inject type from join via raw sql HOT 2
- Set role & configs HOT 2
- dropTable temporary modifier
- Ms sql server - database / schema / tablename HOT 3
- Autocomplete issue with TS 5.0.2 HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from kysely.