Closed andrewsantarin closed 3 years ago
One other thing:
The point of having additional TypeScript tests was to ensure that the declarations worked just as advertised. I do realize that this could be overkill for a library that is still written in plain JavaScript. I rushed quickly into ensuring that the TypeScript side doesn't go to public with at least some quality assurance.
So, in the spirit of keeping things lean, perhaps just dropping the .test.ts
files altogether sounds about good right now.
consolidating the ts/js tests
If we had to introduce TypeScript to tests here, some supplementary (NOT replacement!) tooling for it is in order, e.g. ts-jest
. I do use this at work and it has worked pretty well so far. We don't have to address it right here right now if this is a huge scope creep. I'm glad that we made it to official TypeScript support at this rate.
100% on ts-jest
. Let's do that as a follow up!
:tada: This PR is included in version 8.1.1 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
This PR discards the usage of
tsd
in tests because it has very limited use in this library at the moment.Resolves https://github.com/patw0929/react-intl-tel-input/pull/389#discussion_r688971979
Description
tsd
usage, dependency and mention.Screenshots (if appropriate):
Not required. This is a development workflow change.
Types of changes
Checklist: