Skip to content

Commit d6fa6bd

Browse files
merging all conflicts
2 parents 97cb8d8 + d2ade76 commit d6fa6bd

17 files changed

+116
-6
lines changed

content/blog/2018-11-27-react-16-roadmap.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -175,7 +175,7 @@ function App() {
175175
// provide Suspense integrations with similar APIs.
176176
```
177177

178-
There is no official documentation for how to fetch data with Suspense yet, but you can find some early information in [this talk](https://youtu.be/ByBPyMBTzM0?t=1312) and [this small demo](https://github.com/facebook/react/tree/master/fixtures/unstable-async/suspense). We'll write documentation for React Cache (and how to write your own Suspense-compatible library) closer to this React release, but if you're curious, you can find its very early source code [here](https://github.com/facebook/react/blob/master/packages/react-cache/src/ReactCache.js).
178+
There is no official documentation for how to fetch data with Suspense yet, but you can find some early information in [this talk](https://youtu.be/ByBPyMBTzM0?t=1312) and [this small demo](https://github.com/facebook/react/blob/master/packages/react-devtools/CHANGELOG.md#suspense-toggle). We'll write documentation for React Cache (and how to write your own Suspense-compatible library) closer to this React release, but if you're curious, you can find its very early source code [here](https://github.com/facebook/react/blob/master/packages/react-cache/src/ReactCache.js).
179179

180180
The low-level Suspense mechanism (suspending rendering and showing a fallback) is expected to be stable even in React 16.6. We've used it for code splitting in production for months. However, the higher-level APIs for data fetching are very unstable. React Cache is rapidly changing, and will change at least a few more times. There are some low-level APIs that are [missing](https://github.com/reactjs/rfcs/pull/89) for a good higher-level API to be possible. We don't recommend using React Cache anywhere except very early experiments. Note that React Cache itself isn't strictly tied to React releases, but the current alphas lack basic features as cache invalidation, and you'll run into a wall very soon. We expect to have something usable with this React release.
181181

content/community/articles.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,3 +16,4 @@ permalink: community/articles.html
1616
- [The Hands-On Guide to Learning React Hooks](https://www.telerik.com/kendo-react-ui/react-hooks-guide/) - Eric Bishard's step-by-step guide to learning React Hooks.
1717
- [How to Use the React Profiler Component to Measure Render Performance](https://medium.com/@adamhenson/how-to-use-the-react-profiler-component-to-measure-performance-improvements-from-hooks-d43b7092d7a8) - Adam Henson's article exemplifying a use case for `<React.Profiler />`.
1818
- [Thinking in React Hooks](https://wattenberger.com/blog/react-hooks) - Amelia Wattenberger's provides visualizations and highlighting the mindset change needed switching from classes to functional components + hooks.
19+
- [React/Redux Links](https://github.com/markerikson/react-redux-links) - Curated tutorial and resource links by Mark Erikson collected on React, Redux, ES6, and more. Very helpful for all kind of developers because of it's categorised content.

content/community/conferences.md

Lines changed: 15 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,11 @@ Do you know of a local React.js conference? Add it here! (Please keep the list c
1212

1313
## Upcoming Conferences {#upcoming-conferences}
1414

15+
### React Summit 2019 {#reactsummit2019}
16+
November 30, 2019 in Lagos, Nigeria
17+
18+
[Website](https://reactsummit2019.splashthat.com) -[Twitter](https://twitter.com/react_summit)
19+
1520
### React Conf 2019 {#react-conf-2019}
1621
October 24-25, 2019 in Henderson, Nevada USA
1722

@@ -37,6 +42,11 @@ February 27 & 28, 2020 in Sydney, Australia
3742

3843
[Website](https://reactconfau.com/) - [Twitter](https://twitter.com/reactconfau) - [Facebook](https://www.facebook.com/reactconfau) - [Instagram](https://www.instagram.com/reactconfau/)
3944

45+
### React Summit Amsterdam 2020 {#react-summit-2020}
46+
April 15-17, 2020 in Amsterdam, The Netherlands
47+
48+
[Website](https://reactsummit.com) - [Twitter](https://twitter.com/reactamsterdam) - [Facebook](https://www.facebook.com/reactamsterdam) - [Videos](https://youtube.com/c/ReactConferences)
49+
4050
### Render-Atlanta 2020 {#render-atlanta-2020}
4151
May 4-6, 2020. Atlanta, GA, USA.
4252

@@ -85,12 +95,12 @@ November 2-4 in Bratislava, Slovakia
8595
### React.js Conf 2016 {#reactjs-conf-2016}
8696
February 22 & 23 in San Francisco, CA
8797

88-
[Website](http://conf.reactjs.com/) - [Schedule](http://conf.reactjs.com/schedule.html) - [Videos](https://www.youtube.com/playlist?list=PLb0IAmt7-GS0M8Q95RIc2lOM6nc77q1IY)
98+
[Website](http://conf2016.reactjs.org/) - [Schedule](http://conf2016.reactjs.org/schedule.html) - [Videos](https://www.youtube.com/playlist?list=PLb0IAmt7-GS0M8Q95RIc2lOM6nc77q1IY)
8999

90100
### React Amsterdam 2016 {#react-amsterdam-2016}
91101
April 16 in Amsterdam, The Netherlands
92102

93-
[Website](https://react.amsterdam) - [Twitter](https://twitter.com/reactamsterdam) - [Facebook](https://www.facebook.com/reactamsterdam) - [Videos](https://youtube.com/c/ReactConferences)
103+
[Website](https://reactsummit.com) - [Twitter](https://twitter.com/reactamsterdam) - [Facebook](https://www.facebook.com/reactamsterdam) - [Videos](https://youtube.com/c/ReactConferences)
94104

95105
### ReactEurope 2016 {#reacteurope-2016}
96106
June 2 & 3 in Paris, France
@@ -140,7 +150,7 @@ March 28th at the [QEII Centre, London](http://qeiicentre.london/)
140150
### React Amsterdam 2017 {#react-amsterdam-2017}
141151
April 21st in Amsterdam, The Netherlands
142152

143-
[Website](https://react.amsterdam) - [Twitter](https://twitter.com/reactamsterdam) - [Videos](https://youtube.com/c/ReactConferences)
153+
[Website](https://reactsummit.com) - [Twitter](https://twitter.com/reactamsterdam) - [Videos](https://youtube.com/c/ReactConferences)
144154

145155
### ReactEurope 2017 {#reacteurope-2017}
146156
May 18th & 19th in Paris, France
@@ -245,7 +255,7 @@ March 31 in Kiev, Ukraine
245255
### React Amsterdam 2018 {#react-amsterdam-2018}
246256
April 13 in Amsterdam, The Netherlands
247257

248-
[Website](https://react.amsterdam) - [Twitter](https://twitter.com/reactamsterdam) - [Facebook](https://www.facebook.com/reactamsterdam)
258+
[Website](https://reactsummit.com) - [Twitter](https://twitter.com/reactamsterdam) - [Facebook](https://www.facebook.com/reactamsterdam)
249259

250260
### React Finland 2018 {#react-finland-2018}
251261
April 24-26 in Helsinki, Finland
@@ -350,7 +360,7 @@ April 4-5, 2019 in Kraków, Poland
350360
### React Amsterdam 2019 {#react-amsterdam-2019}
351361
April 12, 2019 in Amsterdam, The Netherlands
352362

353-
[Website](https://react.amsterdam) - [Twitter](https://twitter.com/reactamsterdam) - [Facebook](https://www.facebook.com/reactamsterdam) - [Videos](https://youtube.com/c/ReactConferences)
363+
[Website](https://reactsummit.com) - [Twitter](https://twitter.com/reactamsterdam) - [Facebook](https://www.facebook.com/reactamsterdam) - [Videos](https://youtube.com/c/ReactConferences)
354364

355365
### React Finland 2019 {#react-finland-2019}
356366
April 24-26 in Helsinki, Finland

content/community/meetups.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -102,6 +102,7 @@ Do you have a local React.js meetup? Add it here! (Please keep the list alphabet
102102

103103
## Philippines {#philippines}
104104
* [Manila](https://www.meetup.com/reactjs-developers-manila/)
105+
* [Manila - ReactJS PH](https://www.meetup.com/ReactJS-Philippines/)
105106

106107
## Poland {#poland}
107108
* [Warsaw](https://www.meetup.com/React-js-Warsaw/)
@@ -130,6 +131,8 @@ Do you have a local React.js meetup? Add it here! (Please keep the list alphabet
130131
* [Austin, TX - ReactJS](https://www.meetup.com/ReactJS-Austin-Meetup/)
131132
* [Boston, MA - ReactJS](https://www.meetup.com/ReactJS-Boston/)
132133
* [Boston, MA - React Native](https://www.meetup.com/Boston-React-Native-Meetup/)
134+
* [Charlotte, NC - ReactJS](https://www.meetup.com/ReactJS-Charlotte/)
135+
* [Charlotte, NC - React Native](https://www.meetup.com/cltreactnative/)
133136
* [Chicago, IL - ReactJS](https://www.meetup.com/React-Chicago/)
134137
* [Columbus, OH - ReactJS](https://www.meetup.com/ReactJS-Columbus-meetup/)
135138
* [Dallas, TX - ReactJS](https://www.meetup.com/ReactDallas/)

content/community/tools-ui-components.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -82,3 +82,4 @@ permalink: community/ui-components.html
8282
* **[KendoReact](https://www.telerik.com/kendo-react-ui/)**: UI for React Developers.
8383
* **[Mobiscroll React UI Components](https://mobiscroll.com/react)** Mobile UI Controls for the Productive React Developer.
8484
* **[React UI Toolkit](https://react-ui-tools.com/)**: 115+ professionally maintainted UI components ranging from a robust grid to charts and more. Try for FREE and build React apps faster.
85+
* **[Flatlogic React Admin Templates](https://flatlogic.com/templates/react)** 5+ Paid and Free React Admin templates with a lot of components to speed up web development. No jQuery.

content/docs/getting-started.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,11 @@ React를 사용하는데 관심이 있다면, 온라인 코드 편집기를 사
4646

4747
### 새 React 앱 만들기 {#create-a-new-react-app}
4848

49+
<<<<<<< HEAD
4950
React 프로젝트를 시작한다면 [스크립트 태그를 사용한 간단한 HTML 페이지](/docs/create-a-new-react-app.html)를 만드는 것이 최고의 방법일 것입니다. 설치하는 데 1분밖에 걸리지 않습니다!
51+
=======
52+
When starting a React project, a [simple HTML page with script tags](/docs/add-react-to-a-website.html) might still be the best option. It only takes a minute to set up!
53+
>>>>>>> d2ade76cce133af47ab198188fa2de03fa51834b
5054
5155
그러나 애플리케이션이 커진다면 보다 통합된 설정을 고려하는 것이 좋습니다. 대규모 애플리케이션에 권장되는 [여러 개의 JavaScript 툴체인들](/docs/create-a-new-react-app.html)이 있습니다. 각 툴체인은 많은 설정 없이 작동할 수 있고 풍부한 React 에코시스템을 최대한 활용할 수 있습니다.
5256

@@ -115,7 +119,11 @@ React 문서는 Javascript 프로그래밍에 익숙한 사람을 대상으로
115119

116120
트위터의 [@reactjs 계정](https://twitter.com/reactjs)을 팔로우할 수도 있지만, 블로그만 읽어도 꼭 알아야 하는 정보는 놓치지 않을 수 있습니다.
117121

122+
<<<<<<< HEAD
118123
모든 React 릴리즈가 자체 블로그 게시물을 사용할 만한 것은 아니지만 [릴리즈](https://github.com/facebook/react/releases) 페이지와 React의 [`CHANGELOG.md` 파일](https://github.com/facebook/react/blob/master/CHANGELOG.md)에서 모든 릴리즈에 대한 자세한 변경 기록을 확인할 수 있습니다.
124+
=======
125+
Not every React release deserves its own blog post, but you can find a detailed changelog for every release in the [`CHANGELOG.md` file in the React repository](https://github.com/facebook/react/blob/master/CHANGELOG.md), as well as on the [Releases](https://github.com/facebook/react/releases) page.
126+
>>>>>>> d2ade76cce133af47ab198188fa2de03fa51834b
119127
120128
## 버전 관리된 문서 {#versioned-documentation}
121129

content/docs/hooks-reference.md

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -196,7 +196,55 @@ context 객체(`React.createContext`에서 반환된 값)을 받아 그 context
196196
>
197197
>`useContext(MyContext)`는 context를 *읽고* context의 변경을 구독하는 것만 가능합니다. context의 값을 설정하기 위해서는 여전히 트리의 윗 계층에서의 `<MyContext.Provider>`가 필요합니다.
198198
199+
<<<<<<< HEAD
199200
## 추가 Hook {#additional-hooks}
201+
=======
202+
**Putting it together with Context.Provider**
203+
```js{31-36}
204+
const themes = {
205+
light: {
206+
foreground: "#000000",
207+
background: "#eeeeee"
208+
},
209+
dark: {
210+
foreground: "#ffffff",
211+
background: "#222222"
212+
}
213+
};
214+
215+
const ThemeContext = React.createContext(themes.light);
216+
217+
function App() {
218+
return (
219+
<ThemeContext.Provider value={themes.dark}>
220+
<Toolbar />
221+
</ThemeContext.Provider>
222+
);
223+
}
224+
225+
function Toolbar(props) {
226+
return (
227+
<div>
228+
<ThemedButton />
229+
</div>
230+
);
231+
}
232+
233+
function ThemedButton() {
234+
const theme = useContext(ThemeContext);
235+
236+
return (
237+
<button style={{ background: theme.background, color: theme.foreground }}>
238+
I am styled by theme context!
239+
</button>
240+
);
241+
}
242+
```
243+
This example is modified for hooks from a previous example in the [Context Advanced Guide](/docs/context.html), where you can find more information about when and how to use Context.
244+
245+
246+
## Additional Hooks {#additional-hooks}
247+
>>>>>>> d2ade76cce133af47ab198188fa2de03fa51834b
200248
201249
다음의 Hook는 이전 섹션에서의 기본 Hook의 변경이거나 특정한 경우에만 필요한 것입니다. 익히는 것에 너무 압박받지는 마세요.
202250

content/docs/lifting-state-up.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -324,6 +324,10 @@ state를 끌어올리는 작업은 양방향 바인딩 접근 방식보다 더
324324

325325
어떤 값이 props 또는 state로부터 계산될 수 있다면, 아마도 그 값을 state에 두어서는 안 됩니다. 예를 들어 `celsiusValue``fahrenheitValue`를 둘 다 저장하는 대신, 단지 최근에 변경된 `temperature``scale`만 저장하면 됩니다. 다른 입력 필드의 값은 항상 그 값들에 기반해서 `render()` 메서드 안에서 계산될 수 있습니다. 이를 통해 사용자 입력값의 정밀도를 유지한 채 다른 필드의 입력값에 반올림을 지우거나 적용할 수 있게 됩니다.
326326

327+
<<<<<<< HEAD
327328
UI에서 무언가 잘못된 부분이 있을 경우, [React Developer Tools](https://github.com/facebook/react-devtools)를 이용하여 props를 검사하고 state를 갱신할 책임이 있는 컴포넌트를 찾을 때까지 트리를 따라 탐색해보세요. 이렇게 함으로써 소스 코드에서 버그를 추적할 수 있습니다.
329+
=======
330+
When you see something wrong in the UI, you can use [React Developer Tools](https://github.com/facebook/react/tree/master/packages/react-devtools) to inspect the props and move up the tree until you find the component responsible for updating the state. This lets you trace the bugs to their source:
331+
>>>>>>> d2ade76cce133af47ab198188fa2de03fa51834b
328332
329333
<img src="../images/docs/react-devtools-state.gif" alt="Monitoring State in React DevTools" max-width="100%" height="100%">

content/docs/reference-react.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -331,7 +331,11 @@ const SomeComponent = React.lazy(() => import('./SomeComponent'));
331331

332332
### `React.Suspense` {#reactsuspense}
333333

334+
<<<<<<< HEAD
334335
`React.Suspense`를 사용하면 트리 상에 아직 렌더링이 준비되지 않은 컴포넌트가 있을 때 로딩 지시기(Loading indicator)를 나타낼 수 있습니다. 현재로서는 지연시켜서 불러오는 컴포넌트가 `<React.Suspense>`**유일한** 사용 사례입니다.
336+
=======
337+
`React.Suspense` lets you specify the loading indicator in case some components in the tree below it are not yet ready to render. Today, lazy loading components is the **only** use case supported by `<React.Suspense>`:
338+
>>>>>>> d2ade76cce133af47ab198188fa2de03fa51834b
335339

336340
```js
337341
// 이 컴포넌트는 동적으로 불러옵니다

content/docs/uncontrolled-components.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,11 @@ title: 비제어 컴포넌트
44
permalink: docs/uncontrolled-components.html
55
---
66

7+
<<<<<<< HEAD
78
대부분 경우에 폼을 구현하는데 [제어 컴포넌트](/docs/forms.html)를 사용하는 것이 좋습니다. 제어 컴포넌트에서 폼 데이터는 React 컴포넌트에서 다루어집니다. 대안인 비제어 컴포넌트는 DOM 자체에서 폼 데이터가 다루어집니다.
9+
=======
10+
In most cases, we recommend using [controlled components](/docs/forms.html#controlled-components) to implement forms. In a controlled component, form data is handled by a React component. The alternative is uncontrolled components, where form data is handled by the DOM itself.
11+
>>>>>>> d2ade76cce133af47ab198188fa2de03fa51834b
812
913
모든 state 업데이트에 대한 이벤트 핸들러를 작성하는 대신 비제어 컴포넌트를 만들려면 [ref를 사용](/docs/refs-and-the-dom.html)하여 DOM에서 폼 값을 가져올 수 있습니다.
1014

gatsby-config.js

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -159,5 +159,20 @@ module.exports = {
159159
},
160160
'gatsby-plugin-react-helmet',
161161
'gatsby-plugin-catch-links',
162+
{
163+
resolve: `gatsby-plugin-manifest`,
164+
options: {
165+
name: 'React Docs',
166+
short_name: 'React', // eg. React [%LANG_CODE%]
167+
// Translators: please change this and two above options (see https://www.gatsbyjs.org/packages/gatsby-plugin-manifest/#feature-configuration---optional)
168+
lang: 'en',
169+
start_url: '/',
170+
background_color: '#20232a',
171+
theme_color: '#20232a',
172+
display: 'standalone',
173+
icon: 'static/logo-512x512.png',
174+
legacy: true,
175+
},
176+
},
162177
],
163178
};

src/components/LayoutFooter/Footer.js

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,9 @@ const Footer = ({layoutHasSidebar = false}: {layoutHasSidebar: boolean}) => (
3131
[media.size('sidebarFixed')]: {
3232
paddingTop: 40,
3333
},
34+
'@media print': {
35+
display: 'none',
36+
},
3437
}}>
3538
<Container>
3639
<div

src/components/LayoutHeader/Header.js

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,9 @@ const Header = ({location}: {location: Location}) => (
2929
width: '100%',
3030
top: 0,
3131
left: 0,
32+
'@media print': {
33+
display: 'none',
34+
},
3235
}}>
3336
<Container>
3437
<div

src/html.js

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,11 @@ export default class HTML extends React.Component {
1919
content="width=device-width, initial-scale=1.0"
2020
/>
2121
<link rel="icon" href="/favicon.ico" />
22+
23+
<meta name="apple-mobile-web-app-capable" content="yes" />
24+
<link rel="apple-touch-icon" href="/logo-180x180.png" />
25+
<meta name="apple-mobile-web-app-title" content="React" />
26+
2227
{this.props.headComponents}
2328
</head>
2429
<body {...this.props.bodyAttributes}>

static/_redirects

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,3 +2,4 @@
22
/tips/controlled-input-null-value.html /docs/forms.html#controlled-input-null-value
33
/hooks /docs/hooks-intro.html
44
/tutorial /tutorial/tutorial.html
5+
/your-story https://www.surveymonkey.co.uk/r/MVQV2R9 301

static/logo-180x180.png

9.43 KB
Loading

static/logo-512x512.png

41.4 KB
Loading

0 commit comments

Comments
 (0)