2 replies

How should I handle differences in frontend TS types vs database schema?

For example, lets say in my SQLite database I have a

Posts p

Posts p

table with the columns

post_id, (fk) user_id, content

post_id, (fk) user_id, content

. Assume other tables exist.

But then in my UI I have a TS type

Post

Post

that looks like

{ post_id: string; username: string; content: string; messages: Message[] }

{ post_id: string; username: string; content: string; messages: Message[] }

This is for a personal practice application and I am not using an ORM. I just want to get an idea of how I could approach building a full stack application from mostly scratch.

Thanks.

TTC

Theo's Typesafe Cult•13mo ago•

2 replies

dabrianator

How should I handle differences in frontend TS types vs database schema?

For example, lets say in my SQLite database I have a

Posts p

Posts p

table with the columns

post_id, (fk) user_id, content

post_id, (fk) user_id, content

. Assume other tables exist.

But then in my UI I have a TS type

Post

Post

that looks like

{ post_id: string; username: string; content: string; messages: Message[] }

{ post_id: string; username: string; content: string; messages: Message[] }

This is for a personal practice application and I am not using an ORM. I just want to get an idea of how I could approach building a full stack application from mostly scratch.

Thanks.

How should I handle differences in frontend TS types vs database schema?

Similar Threads

How should I handle differences in frontend TS types vs database schema?

Similar Threads

Similar Threads

Similar Threads