Merge branch 'master' into react-api

Author: balazsorban44

TRANSLATION.md

@@ -0,0 +1,122 @@
+# reactjs.org magyar fordítási projekt
+
+Ebben a repoban a hivatalos React dokumentáció magyar fordításán dolgozunk. A fordítás céljáról és egyéb részletekről olvasd el
+[ezt a blogbejegyzést](https://reactjs.org/blog/2019/02/23/is-react-translated-yet.html)
+és/vagy nézd meg [ezt a videót](https://youtu.be/lLE4Jqaek5k). Az egyes
+fordítási projektek állásáról az
+[isreacttranslatedyet.com](https://isreacttranslatedyet.com/) címen
+tájékozódhatsz.
+
+Az eredeti (angol nyelvű) dokumentáció a [reactjs.org](https://reactjs.org)-on
+található, ami egy [Gatsby](https://www.gatsbyjs.org/)-vel készült statikus
+weboldal. Ebből lett forkolva ez a repo, ami majd a magyar változatot
+tartalmazza, mikor elkészült. Jelenleg a dokumentumok kb. fele még eredeti
+nyelvű.
+
+## Fordítók
+
+A fordítást @gergely-nagy és @balazsorban44 kezdték el, örömmel vesszük, ha
+csatlakozol. A projektről a
+[react-translations.slack.com](https://rt-slack-invite.herokuapp.com/) oldal
+ #hu csatornáján is beszélgethetünk.
+
+## Hozzájárulás
+
+A fordítás menete a következező:
+
+1. [Itt választasz](https://github.com/reactjs/hu.reactjs.org/issues/1) fordítandó anyagot és jelzed, hogy elkezdenéd a fordítását.
+1. Indítasz egy forkot, az angol szöveg helyére beírod a magyar fordítást.
+1. Amikor elkészült, küldesz egy PR-t a módosításodról
+
+## Gyakori kifejezések
+
+| English | Magyar |
+| --- | --- |
+| _technical and React-specific_ |
+| declarative | deklaratív |
+| component |  komponens |
+| controlled components | kontrollált komponens |
+| uncontrolled components | kontrollálatlan komponens |
+| render | renderelés |
+| data | adat |
+| application | alkalmazás |
+| external plugins | külső bővítmények |
+| third party plugins | harmadik féltől származó bővítmények |
+| syntax | szintaxis |
+| embedding expressions | kifejezések beágyazása |
+| attributes | attributumok |
+| element | elem |
+| functional component | függvény komponens |
+| function component | függvény komponens |
+| class components | osztály komponensek |
+| composition | kompozíció |
+| inheritance | öröklődés |
+| lifecycle | életciklus |
+| handling events | esemény kezelés |
+| conditional Rendering | feltételes renderelés |
+| operator | operátor |
+| reuse | újrafelhasználás |
+| reusable | újrafelhasználható |
+| shallow rendering | sekély renderelés |
+| deprecated | elavult |
+| legacy | örökség / korábbi |
+| cross-cutting concerns | |
+| HOC | FRK |
+| higher-order-component | felsőbb rendű komponens |
+| reconciliation | |
+| state | állapot |
+| local state | helyi állapot |
+| derived state | származtatott állapot |
+| asserts (logikai kijelentés) | állít |
+| vendor prefix | |
+| fallback | |
+| breaking change | |
+| function signature |  |
+| props / prop | propok / prop |
+| context | kontextus |
+| fragments | töredék |
+| portal | portál |
+| class | osztály |
+| tick | ketyegés |
+| bundle | köteg |
+| package | csomag |
+| consumer | |
+| provider | |
+| PropTypes |  PropTípusok |
+| good/bad | jó/rossz |
+| mixins | mixinek |
+| web components | web komponensek |
+| wrapper | |
+| mutation |  mutáció |
+| _General purpose_ |
+| tutorial | tutoriál |
+| tip | tipp |
+| note | megjegyzés |
+| example | példa |
+| reference | referencia |
+| for example | például |
+| importing | | import/importálás |
+| opt-in | opcionális |
+| section | szekció |
+| overview | áttekintés |
+| try it on CodePen | próbáld ki a CodePenen |
+| _No translation required_ |
+| DOM |
+| UI |
+| ref |
+| Web (use uppercase)|
+| Create React App |
+| polyfill |
+| React |
+| Fiber |
+| hook |
+| stateful |
+| stateless |
+| mock | |
+| callback |
+| Promise | |
+
+## Hasznos források
+
+1. [Angol-magyar informatikai szótár](https://www.tankonyvtar.hu/hu/tartalom/tkt/angol-magyar/index.html)
+2. [IT-Szótár](http://www.itszotar.hu/)

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

@@ -175,7 +175,7 @@ function App() {
 // provide Suspense integrations with similar APIs.
 ```
 
-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).
+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).
 
 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.
 

content/blog/2019-08-08-react-v16.9.0.md

@@ -48,7 +48,7 @@ const userProfile = {
 };
 // This will now warn:
 <a href={userProfile.website}>Profile</a>
-````
+```
 
 **In React 16.9,** this pattern continues to work, but it will log a warning. If you use `javascript:` URLs for logic, try to use React event handlers instead. (As a last resort, you can circumvent the protection with [`dangerouslySetInnerHTML`](/docs/dom-elements.html#dangerouslysetinnerhtml), but it is highly discouraged and often leads to security holes.)
 
@@ -70,7 +70,6 @@ This pattern was almost never used in the wild, and supporting it causes React t
 
 We don't expect most codebases to be affected by this.
 
-
 ## New Features {#new-features}
 
 ### Async [`act()`](/docs/test-utils.html#act) for Testing {#async-act-for-testing}
@@ -89,7 +88,7 @@ An update to SomeComponent inside a test was not wrapped in act(...).
 await act(async () => {
   // ...
 });
-````
+```
 
 This solves the remaining cases where you couldn't use `act()` before, such as when the state update was inside an asynchronous function. As a result, **you should be able to fix all the remaining `act()` warnings in your tests now.**
 
@@ -209,12 +208,12 @@ Refer to the documentation for [detailed installation instructions](/docs/instal
 
 ### React {#react}
 
- * Add `<React.Profiler>` API for gathering performance measurements programmatically. ([@bvaughn](https://github.com/bvaughn) in [#15172](https://github.com/facebook/react/pull/15172))
+* Add `<React.Profiler>` API for gathering performance measurements programmatically. ([@bvaughn](https://github.com/bvaughn) in [#15172](https://github.com/facebook/react/pull/15172))
 * Remove `unstable_ConcurrentMode` in favor of `unstable_createRoot`. ([@acdlite](https://github.com/acdlite) in [#15532](https://github.com/facebook/react/pull/15532))
 
- ### React DOM
+### React DOM {#react-dom}
 
- * Deprecate old names for the `UNSAFE_*` lifecycle methods. ([@bvaughn](https://github.com/bvaughn) in [#15186](https://github.com/facebook/react/pull/15186) and [@threepointone](https://github.com/threepointone) in [#16103](https://github.com/facebook/react/pull/16103))
+* Deprecate old names for the `UNSAFE_*` lifecycle methods. ([@bvaughn](https://github.com/bvaughn) in [#15186](https://github.com/facebook/react/pull/15186) and [@threepointone](https://github.com/threepointone) in [#16103](https://github.com/facebook/react/pull/16103))
 * Deprecate `javascript:` URLs as a common attack surface. ([@sebmarkbage](https://github.com/sebmarkbage) in [#15047](https://github.com/facebook/react/pull/15047))
 * Deprecate uncommon "module pattern" (factory) components. ([@sebmarkbage](https://github.com/sebmarkbage) in [#15145](https://github.com/facebook/react/pull/15145))
 * Add support for the `disablePictureInPicture` attribute on `<video>`. ([@eek](https://github.com/eek) in [#15334](https://github.com/facebook/react/pull/15334))
@@ -229,13 +228,13 @@ Refer to the documentation for [detailed installation instructions](/docs/instal
 * Fix hiding Suspense fallback nodes when there is an `!important` style. ([@acdlite](https://github.com/acdlite) in [#15861](https://github.com/facebook/react/pull/15861) and [#15882](https://github.com/facebook/react/pull/15882))
 * Slightly improve hydration performance. ([@bmeurer](https://github.com/bmeurer) in [#15998](https://github.com/facebook/react/pull/15998))
 
- ### React DOM Server
+### React DOM Server {#react-dom-server}
 
- * Fix incorrect output for camelCase custom CSS property names. ([@bedakb](https://github.com/bedakb) in [#16167](https://github.com/facebook/react/pull/16167))
+* Fix incorrect output for camelCase custom CSS property names. ([@bedakb](https://github.com/bedakb) in [#16167](https://github.com/facebook/react/pull/16167))
 
- ### React Test Utilities and Test Renderer
+### React Test Utilities and Test Renderer {#react-test-utilities-and-test-renderer}
 
- * Add `act(async () => ...)` for testing asynchronous state updates. ([@threepointone](https://github.com/threepointone) in [#14853](https://github.com/facebook/react/pull/14853))
+* Add `act(async () => ...)` for testing asynchronous state updates. ([@threepointone](https://github.com/threepointone) in [#14853](https://github.com/facebook/react/pull/14853))
 * Add support for nesting `act` from different renderers. ([@threepointone](https://github.com/threepointone) in [#16039](https://github.com/facebook/react/pull/16039) and [#16042](https://github.com/facebook/react/pull/16042))
 * Warn in Strict Mode if effects are scheduled outside an `act()` call. ([@threepointone](https://github.com/threepointone) in [#15763](https://github.com/facebook/react/pull/15763) and [#16041](https://github.com/facebook/react/pull/16041))
 * Warn when using `act` from the wrong renderer. ([@threepointone](https://github.com/threepointone) in [#15756](https://github.com/facebook/react/pull/15756))

content/blog/2019-08-15-new-react-devtools.md

@@ -4,7 +4,7 @@ author: [bvaughn]
 ---
 We are excited to announce a new release of the React Developer Tools, available today in Chrome, Firefox, and (Chromium) Edge!
 
-## What's changed?
+## What's changed? {#whats-changed}
 
 A lot has changed in version 4!
 At a high level, this new version should offer significant performance gains and an improved navigation experience.
@@ -14,7 +14,7 @@ It also offers full support for React Hooks, including inspecting nested objects
 
 [Visit the interactive tutorial](https://react-devtools-tutorial.now.sh/) to try out the new version or [see the changelog](https://github.com/facebook/react/blob/master/packages/react-devtools/CHANGELOG.md#400-august-15-2019) for demo videos and more details.
 
-## Which versions of React are supported?
+## Which versions of React are supported? {#which-versions-of-react-are-supported}
 
 **`react-dom`**
 
@@ -26,7 +26,7 @@ It also offers full support for React Hooks, including inspecting nested objects
 * `0`-`0.61`: Not supported
 * `0.62`: Will be supported (when 0.62 is released)
 
-## How do I get the new DevTools?
+## How do I get the new DevTools? {#how-do-i-get-the-new-devtools}
 
 React DevTools is available as an extension for [Chrome](https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi?hl=en) and [Firefox](https://addons.mozilla.org/en-US/firefox/addon/react-devtools/).
 If you have already installed the extension, it should update automatically within the next couple of hours.
@@ -37,14 +37,14 @@ If you use the standalone shell (e.g. in React Native or Safari), you can instal
 npm install -g react-devtools@^4
 ```
 
-## Where did all of the DOM elements go?
+## Where did all of the DOM elements go? {#where-did-all-of-the-dom-elements-go}
 
 The new DevTools provides a way to filter components from the tree to make it easier to navigate deeply nested hierarchies.
 Host nodes (e.g. HTML `<div>`, React Native `<View>`) are *hidden by default*, but this filter can be disabled:
 
 ![DevTools component filters](../images/blog/devtools-component-filters.gif)
 
-## How do I get the old version back?
+## How do I get the old version back? {#how-do-i-get-the-old-version-back}
 
 If you are working with React Native version 60 (or older) you can install the previous release of DevTools from NPM:
 
@@ -70,7 +70,7 @@ yarn build:extension
 # Follow the on-screen instructions to complete installation
 ```
 
-## Thank you!
+## Thank you! {#thank-you}
 
 We'd like to thank everyone who tested the early release of DevTools version 4.
 Your feedback helped improve this initial release significantly.