uber Posts - Answer Overflow

uber

Explore posts from servers

•Created by uber on 10/29/2024 in #help

Evolving form data and typesafety .

I'm building an app where clients submit forms and professionals can subscribe to them. The challenge: Each service (cleaning, plumbing, etc.) has its own unique form structure. Professionals can subscribe to specific services and filter based on form fields (e.g., "only show me residential cleaning jobs"). The main problem: When service forms evolve over time (adding/removing/modifying fields), I need to preserve old submissions exactly as they were submitted. However, this breaks TypeScript/Zod type safety. For example: // Original cleaning form type

type CleaningForm = {
  propertyType: 'residential' | 'commercial';
  size: number;
}

type CleaningForm = {
  propertyType: 'residential' | 'commercial';
  size: number;
}

// Updated cleaning form type (removed a field field)

type CleaningForm {
  //(propertyType was removed)
  size: number;
}

type CleaningForm {
  //(propertyType was removed)
  size: number;
}

export const project = pgTable("project", {
  id: serial("id").primaryKey(),
  clientId: integer("client_id").notNull(),
  serviceId: text("service_id").notNull(),
  formData: jsonb("data").notNull(), // <---- form data store in schemalass jsonb
});

export const project = pgTable("project", {
  id: serial("id").primaryKey(),
  clientId: integer("client_id").notNull(),
  serviceId: text("service_id").notNull(),
  formData: jsonb("data").notNull(), // <---- form data store in schemalass jsonb
});

Now TypeScript/Zod will complains when accessing old submissions in my database as they dont match updated types How do you handle this type safety problem when dealing with historical data that doesn't match your current types? Looking for patterns or approaches that maintain type safety across different versions of the same form.

2 replies

Gaming

Programming