Figure out a way to deal with common types

[alber70g]

Originally posted by @alber70g in #25 (comment)

Yes that's a good one. Maybe we need to work on a base set of types to be used. I'm not a big fan of a separate types library. They can become overused, especially when they're broader than what's used in a function.

E.g.

// defined in @kadena/types
export type SomeGenericType = {
  name: string;
  color: 'blue' | 'red' | 'green';
};


// defined in @kadena/some-lib
import type { SomeGenericType } from '@kadena/types';

function getName({ name }: SomeGenericType) {
  return name;
}

In this example the SomeGenericType is way to broad for the usage. I'd rather have it exported and defined specifically, than made generic:

// defined in @kadena/some-lib
export type MySpecificType = {
  name: string;
};

function getName({ name }: MySpecificType) {
  return name;
}

Also, api-extractor can manage the type defenition .d.ts. generation based on public, alpha, beta, non-private JS/TSdoc

[github-actions]

This issue is stale because it is open for 60 days with no activity