Skip to content

📖Update to use FC and not SFC #113

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

Closed
wants to merge 6 commits into from
Closed

Conversation

Pau1fitz
Copy link

@Pau1fitz Pau1fitz commented Dec 7, 2018

@piotrwitek
Copy link
Owner

piotrwitek commented Dec 7, 2018

Hey, that improvement looks cool!

Please remember about: https://github.com/piotrwitek/react-redux-typescript-guide/blob/master/CONTRIBUTING.md

I can lend a hand during weekend with rebuilding generated code for examples etc.

@piotrwitek
Copy link
Owner

piotrwitek commented Dec 11, 2018

Hey @Pau1fitz did it already landed on @types? How about SFC, will it still be supported or the new @types will be breaking all SFC usages?

@Pau1fitz
Copy link
Author

Hey @piotrwitek, I tried to run the changes through the contributing guideline stages over the weekend, but had some issues. they are just deprecated at the moment, but still work. Would be good to update this guide though as a lot of people use this resource. You can see that this guide uses FunctionComponent.

@piotrwitek
Copy link
Owner

Got it, the reason I'm asking is I was trying it like a few days ago and FC was not part of react types.

I'll try again

@Pau1fitz
Copy link
Author

Pau1fitz commented Dec 12, 2018

cool, let me know 👍🏼

@piotrwitek
Copy link
Owner

OK, checked and working fine.

One more thing, could you please change all instances of "Stateful components" to "Class components"? As of now this distinction will make more sense.

README.md Outdated

#### - stateless counter
#### - functional counter
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

functional counter is a bit confusing name, let's name it "counter component"

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure, sounds good. I just changed it as stateless is no longer the term being used. are you happy for me to do it in this PR, as I said I was having issues with the instructions in the contributing guidelines - it wasn't working  😯

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yea sure.
Could you also post what was the issue with contributing guide as I would like to fix that.
Thanks

@Pau1fitz
Copy link
Author

Pau1fitz commented Dec 12, 2018

Changes updated.

The issue with the contributing guide that I am having is in relation to step 2:

# run type-checking in `/playground` folder
npm run tsc

Lots of errors:

screenshot 2018-12-12 at 15 56 46

@piotrwitek
Copy link
Owner

piotrwitek commented Dec 14, 2018

Changes updated.

The issue with the contributing guide that I am having is in relation to step 2:

# run type-checking in `/playground` folder
npm run tsc

Lots of errors:
...

Thanks.
I guess errors have something to do with how you installed your dependencies, because on clean install there aren't any errors.

Did you install dependencies with npm at least [email protected] to respect package-lock?

@Pau1fitz
Copy link
Author

I am using npm v 6.4.1

@piotrwitek
Copy link
Owner

Have you tried to rm -rf node_modules and then do a clean install?

@piotrwitek
Copy link
Owner

piotrwitek commented Jan 24, 2019

Rebased your work on master, updated readme-source, updated source files in playground, updated styleguidist webpage.

Merged in #124 & #125

@piotrwitek piotrwitek closed this Jan 24, 2019
@Pau1fitz
Copy link
Author

thanks @piotrwitek good work

@Pau1fitz Pau1fitz deleted the patch-1 branch January 24, 2019 13:39
@piotrwitek
Copy link
Owner

piotrwitek commented Jan 24, 2019

@Pau1fitz Thanks for the initial work! I wanted to retain your contribution but when I squashed and merged the PR github didn't honored it. Sorry for that I will need to check some guide how to do it properly next time.

@Pau1fitz
Copy link
Author

will have to make another PR 😁🤓

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants