Skip to content

Update docs for stable Hooks #1593

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.

Sign up for GitHub

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
gaearon wants to merge 21 commits into from
Closed

Update docs for stable Hooks #1593

Changes from 1 commit
Commits
Show all changes
21 commits
Select commit Hold shift + click to select a range
08b6e4b
Update docs for stable Hooks
gaearon Jan 24, 2019
4d61b4a
Add Hooks to reference page
gaearon Jan 25, 2019
f510e11
Reword intro
gaearon Jan 25, 2019
9d62821
Tweak refwording
gaearon Jan 25, 2019
eaefc81
Hooks blog post draft
gaearon Jan 25, 2019
57138d7
Link to roadmap from post
gaearon Jan 25, 2019
5da272a
Add more details
gaearon Jan 29, 2019
e9081c7
Update and rename 2019-01-30-react-v16.8.0.md to 2019-02-04-react-v16…
gaearon Jan 29, 2019
d15ec6e
changelog updates
gaearon Feb 1, 2019
37d46dd
review tweaks
gaearon Feb 1, 2019
ee5fea9
Mention type defs
gaearon Feb 1, 2019
e301239
add warning for invalid hook call
gaearon Feb 1, 2019
2fd487e
Update 2019-02-04-react-v16.8.0.md
gaearon Feb 4, 2019
ed6e711
Thanks Sophie
gaearon Feb 4, 2019
0d89570
Update 2019-02-04-react-v16.8.0.md
gaearon Feb 4, 2019
95258c0
Revert "add warning for invalid hook call"
gaearon Feb 4, 2019
e5a987b
Tweaks
gaearon Feb 4, 2019
d460a9b
Docs updates
gaearon Feb 4, 2019
f9f0d66
Point to codesandbox and usehooks as community examples
gaearon Feb 5, 2019
d97cdca
tweaks
gaearon Feb 5, 2019
601c016
testing
gaearon Feb 5, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Mention type defs
  • Loading branch information
@gaearon
gaearon committed Feb 1, 2019
commit ee5fea9f36c9e6cbeaff0b494160a180dd27075f
2 changes: 2 additions & 0 deletions content/blog/2019-02-04-react-v16.8.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,8 @@ Note that **to enable Hooks, all React packages need to be 16.8.0 or higher**. H

**React Native will fully support Hooks in its next stable release.**
Copy link
Member

@sophiebits sophiebits Feb 4, 2019

Choose a reason for hiding this comment

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

can we include a version number?


The final TypeScript and Flow definitions are currently in review and will be available soon.
Copy link

@Jessidhia Jessidhia Feb 3, 2019 •
edited
Loading

Choose a reason for hiding this comment

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

It was actually accidentally merged early and is already available in @types/react@16.8.1 😅

Fortunately the only part that is not compatible for current alpha users is the 3rd argument to useReduce.

Copy link

@Jessidhia Jessidhia Feb 4, 2019 •
edited
Loading

Choose a reason for hiding this comment

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

To clarify, the DefinitelyTyped publish bot does an auto-publish, with a patch version bump, every time a PR is merged. There were 2 PRs to update the API so the first publish to have both was 16.8.1.


## Tooling Support

React Hooks are now fully supported by React DevTools. They are also supported in the latest Flow and TypeScript definitions for React. We strongly recommend enabling a new [lint rule called `eslint-plugin-react-hooks`](https://www.npmjs.com/package/eslint-plugin-react-hooks) to enforce best practices with Hooks. It will soon be included into Create React App by default.
Copy link

@resolritter resolritter Feb 2, 2019

Choose a reason for hiding this comment

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

I'll take the opportunity to ask a question if you don't mind. I noticed that hooks' values aren't easily editable like class properties in the DevTools, which was a surprise for me.

react

Although they could be considered "fully-supported" in the sense of what's possible to do in regards to implementation details, I'd think the passage also implies feature-parity with the way people are used to interact with class components.

The way the sentence is structured implies a solved problem. Is it the case? Or will hooks' values also be as flexible in the future?

Expand Down