You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for putting this lib together and providing a way to test type declarations that aren't part of DefinitelyTyped easily. I am also aware that both take different approaches and have different constraints.
Question
I would like to know if adding the possibility to disable the rules would make sense? AFAIK such option isn't present yet?
Context
I ask that question as I working on a compiler that generates declaration files (not from tsc). Now, I need to add tests on the
generated declaration files, in a unit test folder, so that I can ensure that the compiler generates the correct types and detect regressions over time.
That's my current pain point, those declaration files aren't part of a lib that intends to be published on any registry. They are tests fixtures for which I would like to write some tests (on types). As such, those files aren't part of the files property in the package.json file and trying to use tsd in that setup just fail returning me the error from the files-property rule.
I am aware that my use case is a bit a stretch from what tsd is designed to handle (testing types as a lib author) but if such a use case would make sense and is acceptable with what the lib intends to do I am willing to put some time or at least collaborate on this.
The text was updated successfully, but these errors were encountered:
Hi,
Thank you for putting this lib together and providing a way to test type declarations that aren't part of DefinitelyTyped easily. I am also aware that both take different approaches and have different constraints.
Question
I would like to know if adding the possibility to disable the rules would make sense? AFAIK such option isn't present yet?
Context
I ask that question as I working on a compiler that generates declaration files (not from
tsc
). Now, I need to add tests on thegenerated declaration files, in a unit test folder, so that I can ensure that the compiler generates the correct types and detect regressions over time.
That's my current pain point, those declaration files aren't part of a lib that intends to be published on any registry. They are tests fixtures for which I would like to write some tests (on types). As such, those files aren't part of the
files
property in thepackage.json
file and trying to usetsd
in that setup just fail returning me the error from thefiles-property
rule.I am aware that my use case is a bit a stretch from what
tsd
is designed to handle (testing types as a lib author) but if such a use case would make sense and is acceptable with what the lib intends to do I am willing to put some time or at least collaborate on this.The text was updated successfully, but these errors were encountered: