feat: also export the type Test
#57
Conversation
Codecov Report
@@ Coverage Diff @@
## master #57 +/- ##
=======================================
Coverage 90.16% 90.16%
=======================================
Files 3 3
Lines 305 305
=======================================
Hits 275 275
Misses 30 30 Continue to review full report at Codecov.
|
| @@ -17,7 +17,10 @@ declare namespace uvu { | |||
| } | |||
|
|
|||
| type Context = Record<string, any>; | |||
| export const test: uvu.Test<Context>; | |||
|
|
|||
| export type Test<T=Context> = uvu.Test<T>; | |||
There was a problem hiding this comment.
I didn't have this exposed because of the generic naming.
But now that it is, what do you think about using the Suite name instead, since that's what it is?
There was a problem hiding this comment.
I mean you could argue the same thing with Callback. To me the suite, is the collection of test's (at least mentally), and a Test is the individual units. Seeing as suite() returns a uvu.Test it's only fitting to also export that type.
Its like you don't share suites, you share tests. I know its the same thing—but i still believe the naming her is right.
I want to share my
tests. Kind of to create this partial concept. And for that, I would like my types to "accept" aTesttype.