-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TS Migration: addon-notes #4758
Conversation
Changed file names for being more clear
Currently working on a fix for imports It should import from |
Added 'types' file path in package.json Moved addon-notes tsconfig configurations into the root tsconfig
@ndelangen I added comments to my initial post. Feel free to check the changes and ask me questions - or lets talk later this week 🙂 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice start! I've added a few comments about React-TS specific stuff.
Codecov Report
@@ Coverage Diff @@
## next #4758 +/- ##
==========================================
+ Coverage 34.94% 35.06% +0.12%
==========================================
Files 566 563 -3
Lines 7020 6970 -50
Branches 937 932 -5
==========================================
- Hits 2453 2444 -9
+ Misses 4071 4031 -40
+ Partials 496 495 -1 Continue to review full report at Codecov.
|
Also had to introduce a couple of new any assignments because of noImplicitAny: true They still need to be resolved. WIP
# Conflicts: # addons/notes/package.json # package.json # yarn.lock
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm
As discussed here https://stackoverflow.com/questions/41746028/proptypes-in-a-typescript-react-application#comment80415295_43187969 I should add prop types again because non-typescript consumers don't profit from definition files |
…s for non-typescript users
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, otherwise there is one small comment to improve.
Issue: N/A
What I did
@ndelangen and I talked about doing a POC for TypeScript in Storybook
This POC needs to answer the following questions:
ts
*.js
to*.ts
also might cause a couple of red lines. Mostly imports that must be used differently or type mismatches.Danger
everything's green 🙂tslint
was already configured. I have not noticed any weird linting errorsyarn dev
should not get significantly slower as it is right nowyarn dev:ts
is super fast,yarn dev
is slow as usual ;)What I found out
tslint.json
already exists in the root directory, must check if it worksyarn dev:ts
already searches fortsconfig.json
files inside all workspaces. If it found one, it compiles the project to.js
.tsx
files can be compiled to.js
as wellSome side notes