Sound arg types for CSF3

[kasperpeulen]

Strict args

export type StoryAnnotations<
  TFramework extends AnyFramework = AnyFramework,
  TArgs = Args,
  TArgsAnnotations = Partial<TArgs>
> 

Added a third argument, for the args that need to be annotated for a story (which may be different then "all" the args, which is TArgs). This allows frameworks to provide strict args without specifying args that are already filled in automagically.

Strict component in meta:
Made AnyFramework dependent on a generic parameter T, which makes sure we can use the Framework['component'] with different generic values ( we use any/unknown,TArgs).

This ensures that the component provided in meta, must match TArgs, while subcomponents and other references of Framework['component'] stay more generic.

Strict decorators/loaders:
Loaders and decorators are now dependent on TArgs, which means you get auto-completion and typesafety when using args.

decorators: [(Story, { args }) => (
    <>
      Decorator: {args.sometingOnTArgs}
      <Story args={{ otherThingonTArgs: 0 }} /> // I also changed this to accept {args?: Partial<TArgs>} instead of {args?: TArgs}
    </>
  )
]

📦 Published PR as canary version: 0.0.2--canary.49.65292c2.0

✨ Test out this PR locally via:

npm install @storybook/[email protected]
# or 
yarn add @storybook/[email protected]

[tmeasday]

LGTM, I have a couple questions for my own clarification, and one minor suggestion.

[tmeasday]

Suggested change

	TArgsAnnotations = Partial<TArgs>
	TRequiredArgs = Partial<TArgs>

This is more intuitive to me, what do you think?

[kasperpeulen]

Sounds good to me, what do you think @shilman?

[shilman]

Works for me. Also discussed TRemainingArgs because these args are not necessarily required. But agree that "required" is the most readable/clear

[shilman]

🚀 PR was released in v0.1.0 🚀