Introduction

Working With Monorepos

Workspaces

Shared Configs

Frontend

Schema

Backend

Introduction and Getting Started

Analyzing

Designing the Customer-facing UI with TailwindCSS

Data Model

Analysis and Design

PostgreSQL Ranges

The Provider Table

The Booking Table

Modelling with advanced Postgres features

Tailwind CSS

Foundation

Frontend State

Shared Components

Select Day

Frontend UI

Introducing tRPC

Connecting to tRPC

Refining the tRPC setup

Connecting to the Database

Generating Zod schemas

Endpoints

Testing tRPC Endpoints

Testing With the Database

Testing Frontend

Testing

Completing the Select Date Page

Infrastructure for Ranges

Completing Booking

Connecting The Dots

Conclusion and extra resources

This comprehensive course will equip you with the skills and knowledge to build modern full-stack applications using TypeScript, TailwindCSS, tRPC, and PostgreSQL. You will learn how to create a robust and scalable application architecture, from the backend data layer to the frontend UI.

PostgreSQL

NodeJS

Knex

React

TypeScript

tRPC

Monorepos simplify code development and can be split when necessary.

Setting up npm workspaces in our monorepo

Setting up shared Typescript, ESLint and Prettier configs

Master full-stack development with a single repository for everything!

Learn the art of full-stack development with this comprehensive course. Through implementing the latest technologies and techniques, the course directly addresses the most common challenges full-stack developers face:
- **Code consistency and sharing:** Monorepos eliminate the need for multiple repositories, ensuring consistent code across your application and facilitating seamless code sharing.
- **Technology integration:** Learn how to integrate modern technologies like TypeScript, Tailwind CSS, and tRPC, empowering you to build robust and maintainable applications.
- **Database management:** Master advanced PostgreSQL features to optimize data storage, retrieval, and manipulation, ensuring a high-performance and scalable backend.

Build type-safe full-stack applications with database-centric strategies

This comprehensive full-stack development course covers monorepos, TypeScript, Tailwind CSS, tRPC, and PostgreSQL, empowering you to build modern, scalable applications. Structured into 7 modules of bite-sized lessons, each module is designed to be engaging and informative, combining video lectures, hands-on coding exercises, and real-world examples.

Fullstack Typescript with TailwindCSS and tRPC Using Modern Features of PostgreSQL

Writing PostgreSQL ranges for the application database.

Breaking down the UI to build it with Tailwind CSS

Master monorepos for streamlined development workflows and enhanced collaboration

Implement TypeScript for type-safe code that prevents errors and improves maintainability

Utilize Tailwind CSS to create consistent and beautiful user interfaces

Employ tRPC for seamless data exchange between frontend and backend

Harness advanced PostgreSQL features for optimized data storage, retrieval, and manipulation

Build modern, scalable full-stack applications using a unified approach

 table, but there are a few things you need to change. You can do this in a kind-of TDD-like fashion by invoking 

. Schemalint can run a set of rules against a database schema and report any violations. You will use Schemalint to check that the schema aligns with your expectations. Start by installing it:

# In the /packages/schema folder:
$ npm i -D schemalint

const knexConfig = require('./knexfile');

module.exports = {
  connection: knexConfig.development.connection,

  rules: {
    'name-casing': ['error', 'snake'],
    'name-inflection': ['error', 'singular'],
    'prefer-jsonb-to-json': ['error'],
    'prefer-text-to-varchar': ['error'],
    'prefer-identity-to-serial': ['error'],
  },

  schemas: [{ name: 'public' }],

  ignores: [
    { identifierPattern: 'public\\.knex_migrations.*', rulePattern: '.*' },
  ],
};

I'll explain this configuration in a bit but first, try and run it:

$ npx schemalint

schema-lint
Connecting to easybooking on 127.0.0.1
public.users: error name-inflection : Expected singular names, but 'users' seems to be plural
public.users.email: error prefer-text-to-varchar : Prefer text to varchar types
public.users.password: error prefer-text-to-varchar : Prefer text to varchar types
public.users.id: error prefer-identity-to-serial : Prefer IDENTITY to type SERIAL

Suggested fix
...

Yikes, there are problems with everything in our schema! It suggests some fixes but we'll ignore those for now. Let's take a look at the configuration file.

We have 5 rules in play. The first two are about naming conventions.

 for table and column names and we want to use singular names for tables. The snake case rule is quite standard for PostgreSQL. It's possible to use upper case in names but you have to then remember to enclose names in quotation marks when you use them in queries. This can lead to some particularly confusing errors that can be hard to debug.

The singular rule is a bit more opinionated. Whether table names should be singular or plural is a topic of great debate. I prefer singular and it has the small benefit that the name maps nicely to a type. In English, most nouns are regular and the inflection is a matter of an S at the end but there are exceptions and for instance, it hurts my eyes to map a 

The remaining rules are about data types.

 is a fixed length type. The official PostgreSQL wiki 

 was more space efficient but that's no longer the case, so by using it you are simply putting unnecessary constraints on the length of your strings.

 type is a binary representation of JSON data. It's more efficient to store and query than 

---
title: The Provider Table
description: Getting properly started with our database schema
isPublicLesson: true
privateVideoUrl: https://stream.mux.com/uZVzRASUWt7LX5gSxKUtUHyokSMxiv3aFYADzHdQnYI.m3u8
code: https://gitlab.com/fullstackio/books/newline-course-apps/fullstack-typescript-with-tailwindcss-and-trpc-using-modern-features-of-postgresql-app/-/tree/main/module_03/lesson_03.02?ref_type=heads
---

## The basic schema

The database already has a `users` table, but there are a few things you need to change. You can do this in a kind-of TDD-like fashion by invoking [Schemalint](https://github.com/kristiandupont/schemalint). Schemalint can run a set of rules against a database schema and report any violations. You will use Schemalint to check that the schema aligns with your expectations. Start by installing it:

```bash
# In the /packages/schema folder:
$ npm i -D schemalint
```

And configure it with a `.schemalintrc.js` file:

```js
const knexConfig = require('./knexfile');

module.exports = {
  connection: knexConfig.development.connection,

  rules: {
    'name-casing': ['error', 'snake'],
    'name-inflection': ['error', 'singular'],
    'prefer-jsonb-to-json': ['error'],
    'prefer-text-to-varchar': ['error'],
    'prefer-identity-to-serial': ['error'],
  },

  schemas: [{ name: 'public' }],

  ignores: [
    { identifierPattern: 'public\\.knex_migrations.*', rulePattern: '.*' },
  ],
};
```

I'll explain this configuration in a bit but first, try and run it:

```bash
$ npx schemalint

schema-lint
Connecting to easybooking on 127.0.0.1
public.users: error name-inflection : Expected singular names, but 'users' seems to be plural
public.users.email: error prefer-text-to-varchar : Prefer text to varchar types
public.users.password: error prefer-text-to-varchar : Prefer text to varchar types
public.users.id: error prefer-identity-to-serial : Prefer IDENTITY to type SERIAL

Suggested fix
...
```

Yikes, there are problems with everything in our schema! It suggests some fixes but we'll ignore those for now. Let's take a look at the configuration file.

We have 5 rules in play. The first two are about naming conventions.

We want to use `snake_case` for table and column names and we want to use singular names for tables. The snake case rule is quite standard for PostgreSQL. It's possible to use upper case in names but you have to then remember to enclose names in quotation marks when you use them in queries. This can lead to some particularly confusing errors that can be hard to debug.

The singular rule is a bit more opinionated. Whether table names should be singular or plural is a topic of great debate. I prefer singular and it has the small benefit that the name maps nicely to a type. In English, most nouns are regular and the inflection is a matter of an S at the end but there are exceptions and for instance, it hurts my eyes to map a `people` table to a `Person` type.

The remaining rules are about data types.

We want to use `text` instead of `varchar`. `text` is a variable length type whereas `varchar` is a fixed length type. The official PostgreSQL wiki [recommends](https://wiki.postgresql.org/wiki/Don't_Do_This#Don.27t_use_varchar.28n.29_by_default) always using `text` instead of `varchar`. In the old days, `varchar` was more space efficient but that's no longer the case, so by using it you are simply putting unnecessary constraints on the length of your strings.

The `jsonb` type is a binary representation of JSON data. It's more efficient to store and query than `json` and it also supports indexing.

Getting properly started with our database schema

Learn

The newline Guide to Building Your First GraphQL Server with Node and TypeScript

Teach

Amelia Wattenberger

Author of Fullstack D3

Community

Fullstack Typescript with TailwindCSS and tRPC Using Modern Features of PostgreSQL

Module 1: Introduction and Getting Started

Introduction:

Start Here

Lesson 1: (3:09)

Introduction

Lesson 2: (6:35)

Working With Monorepos

Lesson 3: (6:45)

Workspaces

Lesson 4: (17:56)

Shared Configs

Lesson 5: (9:27)

Frontend

Lesson 6: (16:20)

Schema

Lesson 7: (5:21)

Backend

Module 2: Analysis and Design

Lesson 1: (3:09)

Analyzing

Lesson 2: (4:04)

Designing the Customer-facing UI with TailwindCSS

Lesson 3: (2:49)

Data Model

Module 3: Modelling with advanced Postgres features

Lesson 1: (6:18)

PostgreSQL Ranges

Lesson 2: (16:10)

The Provider Table

Lesson 3: (4:47)

The Booking Table

Module 4: Frontend UI

Lesson 1: (1:25)

Tailwind CSS

Lesson 2: (7:58)

Foundation

Lesson 3: (21:53)

Frontend State

Lesson 4: (4:52)

Shared Components

Lesson 5: (16:13)

Select Day

Module 5: Endpoints

Lesson 1: (7:45)

Introducing tRPC

Lesson 2: (17:22)

Connecting to tRPC

Lesson 3: (7:22)

Refining the tRPC setup

Lesson 4: (7:28)

Connecting to the Database

Lesson 5: (4:56)

Generating Zod schemas

Module 6: Testing

Lesson 1: (4:33)

Testing tRPC Endpoints

Lesson 2: (25:00)

Testing With the Database

Lesson 3: (12:37)

Testing Frontend

Module 7: Connecting The Dots

Lesson 1: (21:07)

Completing the Select Date Page

Lesson 2: (14:07)

Infrastructure for Ranges

Lesson 3: (15:49)

Completing Booking

Module 8: Conclusion and extra resources

Lesson 1: (1:02)

Conclusion and extra resources

The Provider Table