generated schemda.d.ts is invalid if you have a kebab-case named table

[atomanyih]

Trying out zapatos on an existing codebase and ran into this problem.

If you have a table called kebab-name, it will generate something like this:

declare module 'zapatos/schema' {
  // ...etc
  export namespace kebab-name { // syntax error
    // ...etc...
  }

  export namespace public {  
    export type Table = kebab-name.Table // syntax error
    // ...etc...
  }
}

Now I know that kebab-case is not postgres convention, but unfortunately someone donked up and it is technically valid. I'm wondering if there's any way to work around this that isn't manually correcting the generated schema.d.ts

[jawj]

Hmm, I fixed this for column names recently in #122. But I'm afraid I don't think there's any straightforward fix for tables, because IIRC TypeScript namespaces have to be valid JS identifiers.

[sonhanguyen]

IIRC TypeScript namespaces have to be valid JS identifiers.

We don't have to use the kebab-case, we can just convert it to PascalCase