Default name formatter is too brittle

[runeh]

The default name formatter just uppercases the first letter. This doesn't work for types that use a non-alpha prefix. For example, given a value named _links, we now generate this code:

const _links = rt.Record({next: rt.String, prev: rt.String});

type _links = rt.Static<typeof _links>;

We probably don't want the names to be identical, even though it's technically allowed I think.

[simenandre]

I haven't hit this edge-case yet. Thanks for adding the issue!

[haradzienski]

We actually ended up with a convention like this:

• the runtype name starts with lowercase letter, and has Schema postfix: fooSchema
• the static type name starts with uppercase letter, and does not have any postfixes: Foo

I think that Schema part came from joi world - it was used for runtime schema validation in pre-runtypes ages on my current project. But the point is still valid, we can just append something like Schema or Runtype or even just Rt to the name to get different names even without uppercasing/lowercasing first letters.

[runeh]

Sounds reasonable. My suggestion, add Runtype to runtypes, and uppercase they types like you say? And explain in docs that the behaviour can be overridden by the naming functions.