Extract type definitions that might be used across modules

[Shinigami92]

We have some types like Casing that can be reused be multiple module functions.
Also we might want to extract a Range or an interface that defines a length or range that can then be used by all functions that have a length or min-max signature.

Decision to discuss: We might want to change all length-only signatures to also accept a min-max option.

[xDivisionByZerox]

@ST-DDT Does the rewrite of your docs generation support the resolving of JSDoc information of custom types? Or can we at least make it work?
If I remember correctly this was the previously the problem why we were not able to use custom types. At least for objects interfaces/types that contained properties with JSDocs.

[ST-DDT]

IIRC the current implementation shows the name of the type aka Casing, but it should already resolve it as shadow type but it isnt shown yet. I have somewhat forgotten about the docs rewrite to change the visualization of the docs. If I have some free time, I'll look into it this week.

[ST-DDT]

Just found this issue. What still needs to be done here?

[xDivisionByZerox]

We have Union Types that define the same thing in multipel places. For example:

• faker/src/modules/string/index.ts

  Line 8 in f286dfd

  export type Casing = 'upper' | 'lower' | 'mixed';

• faker/src/modules/color/index.ts

  Line 42 in f286dfd

  export type Casing = 'lower' | 'upper' | 'mixed';

Another idea was to provide a unified interface for ranges that we have in a lot of places (number | { min?: number, max?: number }). That way we would not repeat the documentation in multiple places and had a more unified API.
So far we have not done it, because the autogenerate documentation would not be able to handle it (if I remember correctly).

[ST-DDT]

If you tell me, what you need/expect, maybe I can look into it (apidocs part).