All columns are optional in the resulting definition about sql-ts HOT 7 CLOSED

@rmp135 Alright :-) ! Maybe it could be an option in the config :-)

from sql-ts.

@finneganh In that case I could provide multiple values for the optionality config.
"Required" for your use case - everything is required.
"Dynamic" for column determined values.
"Optional" for how it currently works, everything is optional.

from sql-ts.

This was by design. I'll keep the ticket open but it's not something I'll be adding soon.

from sql-ts.

An option would be neat. In the meantime, I’m using this when I want all the fields to be required:

type RequireAll<Obj extends Object> = { [Field in keyof Obj]-?: Obj[Field] };
export type DbBoard = RequireAll<BoardsEntity>;

from sql-ts.

Given the interest, I'll implement dynamic optionality into the next version.

As a start, columns that have a default value (including auto incrementing) will be set as optional, all others will be required.

I don't know an awful lot about PostgreSQL so if there's any relevant column options that should be looked at, let me know.

from sql-ts.

I think one tension here is if the types are used for input or output. I'm only interested in them for output, so I want to see everything be “required” since that’s what reflects my SELECT *. (If I selected only a few columns I’d probably use TypeScript’s Pick to take them off the all-required version.) If an auto-incrementing column were marked as "optional," I’d have to do null checks (or “!” assertions) even though it would never be null.

But, I can see that if you’re using these to typecheck inputs to a SQL statement, being able to be more optional makes some more sense.

from sql-ts.

This has been implemented in release 0.4.0. Use configuration option propertyOptionality with value required.

from sql-ts.