Skip to content

Commit 265bf37

Browse files
committed
🌐🚧 WIP: translate glossary
1 parent ae8c2fe commit 265bf37

File tree

1 file changed

+27
-27
lines changed

1 file changed

+27
-27
lines changed

content/docs/reference-glossary.md

Lines changed: 27 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -1,63 +1,63 @@
11
---
22
id: glossary
3-
title: Glossary of React Terms
3+
title: React kifejezések szójegyzéke
44
layout: docs
55
category: Reference
66
permalink: docs/glossary.html
77

88
---
99

10-
## Single-page Application {#single-page-application}
10+
## Single-page applikáció {#single-page-application}
1111

12-
A single-page application is an application that loads a single HTML page and all the necessary assets (such as JavaScript and CSS) required for the application to run. Any interactions with the page or subsequent pages do not require a round trip to the server which means the page is not reloaded.
12+
Egy single-page, vagy egyoldalas applikáció egy olyan alkalmazás, ami a futáshoz egyetlen HTML oldalt és az összes szükséges egyéb fájlt (pl.: JavaScript és CSS) tölti be. Bármilyen interakció az oldallal vagy alárendelt oldalakkal nem igényel a szerver felé kérést, ami azt jelenti, az oldal nem töltődik újra.
1313

14-
Though you may build a single-page application in React, it is not a requirement. React can also be used for enhancing small parts of existing websites with additional interactivity. Code written in React can coexist peacefully with markup rendered on the server by something like PHP, or with other client-side libraries. In fact, this is exactly how React is being used at Facebook.
14+
A React-ben tudsz single-page applikációkat készíteni, de ez nem követelmény. A React arra is jó, ha egy létező weboldal kisebb részeit szeretnéd feljavítani extra interaktivitással. A React-ben írt kód békésen együtt tud élni a szerveren renderelt kóddal, mint például PHP, vagy más kliens-oldali könyvtárakkal. Valójában a Facebook-nál is pont így használjuk a React-et.
1515

16-
## ES6, ES2015, ES2016, etc {#es6-es2015-es2016-etc}
16+
## ES6, ES2015, ES2016, stb. {#es6-es2015-es2016-etc}
1717

18-
These acronyms all refer to the most recent versions of the ECMAScript Language Specification standard, which the JavaScript language is an implementation of. The ES6 version (also known as ES2015) includes many additions to the previous versions such as: arrow functions, classes, template literals, `let` and `const` statements. You can learn more about specific versions [here](https://en.wikipedia.org/wiki/ECMAScript#Versions).
18+
Ezek a mozaikszavak mind az ECMAScript nyelv specifikáció standard legújabb verziójaira utalnak aminek a JavaScript nyelv az egyik implementációja. Az ES6-os verzió (ES2015-ként is ismert) sok újdonságot tartalmaz a korábbi verziókhoz képest, mint például: nyíl függvények, osztályok, sablon literálok, `let` és `const` állítások. Az egyes verziókról [itt](https://en.wikipedia.org/wiki/ECMAScript#Versions) tanulhatsz többet.
1919

20-
## Compilers {#compilers}
20+
## Fordítóprogramok {#compilers}
2121

22-
A JavaScript compiler takes JavaScript code, transforms it and returns JavaScript code in a different format. The most common use case is to take ES6 syntax and transform it into syntax that older browsers are capable of interpreting. [Babel](https://babeljs.io/) is the compiler most commonly used with React.
22+
Egy JavaScript fordítóprogram fogja a JavaScript kódot, transzformálja és visszaadja azt JavaScript kódként egy másik formátumban. Leggyakoribb esetben az ES6 szintaxis transzformálására használt, annak érdekében hogy a régebbi böngészők is értelmezni tudják a kódot. A React esetében egyik leggyakrabban használt ilyen fordítóprogram a [Babel](https://babeljs.io/).
2323

24-
## Bundlers {#bundlers}
24+
## Kötegelők {#bundlers}
2525

26-
Bundlers take JavaScript and CSS code written as separate modules (often hundreds of them), and combine them together into a few files better optimized for the browsers. Some bundlers commonly used in React applications include [Webpack](https://webpack.js.org/) and [Browserify](http://browserify.org/).
26+
A kötegelők fogják a különálló (gyakran több száz) modulokban írt JavaScript és CSS kódot , és egyesítik azt néhány böngészőkre jobban optimalizált fájlban. Néhány, a React alkalmazások esetében gyakran használt kötegelő például a [Webpack](https://webpack.js.org/) és a [Browserify](http://browserify.org/).
2727

28-
## Package Managers {#package-managers}
28+
## Csomag kezelők {#package-managers}
2929

30-
Package managers are tools that allow you to manage dependencies in your project. [npm](https://www.npmjs.com/) and [Yarn](https://yarnpkg.com/) are two package managers commonly used in React applications. Both of them are clients for the same npm package registry.
30+
A csomag kezelők olyan eszközök, amik lehetővé teszik egy projekt függőségeinek a kezelését. Az [npm](https://www.npmjs.com/) és a [Yarn](https://yarnpkg.com/) két gyakran használt csomag kezelő a React alkalmazások esetében. Mindkettő egy kliens ugyanazon az npm csomag regisztrátorhoz.
3131

3232
## CDN {#cdn}
3333

34-
CDN stands for Content Delivery Network. CDNs deliver cached, static content from a network of servers across the globe.
34+
A CDN a Content Delivery Network (tartalom szolgáltató hálózat) rövidítése. A CDN-ek gyorsítótárazott, statikus tartalmat szolgáltatnak egy világot átszelő szerverhálón keresztül.
3535

3636
## JSX {#jsx}
3737

38-
JSX is a syntax extension to JavaScript. It is similar to a template language, but it has full power of JavaScript. JSX gets compiled to `React.createElement()` calls which return plain JavaScript objects called "React elements". To get a basic introduction to JSX [see the docs here](/docs/introducing-jsx.html) and find a more in-depth tutorial on JSX [here](/docs/jsx-in-depth.html).
38+
A JSX egy JavaScript szintaxis kiegészítés. Hasonló egy sablon nyelvhez, de a JavaScript teljes erejével rendelkezik. A JSX le van fordítva `React.createElement()` hívásokra, ami egyszerű JavaScript objektumokat térít vissza, amiket "React elemeknek" hívunk. Egy egyszerű bevezetőért [nézd meg a dokumentációt itt](/docs/introducing-jsx.html), egy mélyebbre ható JSX tutoriálért pedig nézd meg [ezt](/docs/jsx-in-depth.html).
3939

40-
React DOM uses camelCase property naming convention instead of HTML attribute names. For example, `tabindex` becomes `tabIndex` in JSX. The attribute `class` is also written as `className` since `class` is a reserved word in JavaScript:
40+
A React DOM camelCase konvenciókat használ tulajdonságok elnevezésére HTML attribútum nevek helyett. Például a `tabindex` JSX-ben `tabIndex`-é válik. A `class` attribútumot is `className`-ként kell írjuk, mivel a `class` a JavaScript-ben egy fenntartott szó:
4141

4242
```js
4343
const name = 'Clementine';
4444
ReactDOM.render(
45-
<h1 className="hello">My name is {name}!</h1>,
45+
<h1 className="hello">A nevem {name}!</h1>,
4646
document.getElementById('root')
4747
);
4848
```
4949

50-
## [Elements](/docs/rendering-elements.html) {#elements}
50+
## [Elemek](/docs/rendering-elements.html) {#elements}
5151

5252
React elements are the building blocks of React applications. One might confuse elements with a more widely known concept of "components". An element describes what you want to see on the screen. React elements are immutable.
5353

5454
```js
55-
const element = <h1>Hello, world</h1>;
55+
const element = <h1>Helló, világ</h1>;
5656
```
5757

5858
Typically, elements are not used directly, but get returned from components.
5959

60-
## [Components](/docs/components-and-props.html) {#components}
60+
## [Komponensek](/docs/components-and-props.html) {#components}
6161

6262
React components are small, reusable pieces of code that return a React element to be rendered to the page. The simplest version of React component is a plain JavaScript function that returns a React element:
6363

@@ -79,7 +79,7 @@ class Welcome extends React.Component {
7979

8080
Components can be broken down into distinct pieces of functionality and used within other components. Components can return other components, arrays, strings and numbers. A good rule of thumb is that if a part of your UI is used several times (Button, Panel, Avatar), or is complex enough on its own (App, FeedStory, Comment), it is a good candidate to be a reusable component. Component names should also always start with a capital letter (`<Wrapper/>` **not** `<wrapper/>`). See [this documentation](/docs/components-and-props.html#rendering-a-component) for more information on rendering components.
8181

82-
### [`props`](/docs/components-and-props.html) {#props}
82+
### [`prop`-ok](/docs/components-and-props.html) {#props}
8383

8484
`props` are inputs to a React component. They are data passed down from a parent component to a child component.
8585

@@ -118,19 +118,19 @@ class Welcome extends React.Component {
118118
}
119119
```
120120

121-
### [`state`](/docs/state-and-lifecycle.html#adding-local-state-to-a-class) {#state}
121+
### [`state`, vagy helyi állapot](/docs/state-and-lifecycle.html#adding-local-state-to-a-class) {#state}
122122

123123
A component needs `state` when some data associated with it changes over time. For example, a `Checkbox` component might need `isChecked` in its state, and a `NewsFeed` component might want to keep track of `fetchedPosts` in its state.
124124

125125
The most important difference between `state` and `props` is that `props` are passed from a parent component, but `state` is managed by the component itself. A component cannot change its `props`, but it can change its `state`.
126126

127127
For each particular piece of changing data, there should be just one component that "owns" it in its state. Don't try to synchronize states of two different components. Instead, [lift it up](/docs/lifting-state-up.html) to their closest shared ancestor, and pass it down as props to both of them.
128128

129-
## [Lifecycle Methods](/docs/state-and-lifecycle.html#adding-lifecycle-methods-to-a-class) {#lifecycle-methods}
129+
## [Életciklus metódusok](/docs/state-and-lifecycle.html#adding-lifecycle-methods-to-a-class) {#lifecycle-methods}
130130

131131
Lifecycle methods are custom functionality that gets executed during the different phases of a component. There are methods available when the component gets created and inserted into the DOM ([mounting](/docs/react-component.html#mounting)), when the component updates, and when the component gets unmounted or removed from the DOM.
132132

133-
## [Controlled](/docs/forms.html#controlled-components) vs. [Uncontrolled Components](/docs/uncontrolled-components.html)
133+
## [Kontrollált](/docs/forms.html#controlled-components) vs. [kontrollálatlan komponensek](/docs/uncontrolled-components.html)
134134

135135
React has two different approaches to dealing with form inputs.
136136

@@ -140,27 +140,27 @@ An *uncontrolled component* works like form elements do outside of React. When a
140140

141141
In most cases you should use controlled components.
142142

143-
## [Keys](/docs/lists-and-keys.html) {#keys}
143+
## [Kulcsok](/docs/lists-and-keys.html) {#keys}
144144

145145
A "key" is a special string attribute you need to include when creating arrays of elements. Keys help React identify which items have changed, are added, or are removed. Keys should be given to the elements inside an array to give the elements a stable identity.
146146

147147
Keys only need to be unique among sibling elements in the same array. They don't need to be unique across the whole application or even a single component.
148148

149149
Don't pass something like `Math.random()` to keys. It is important that keys have a "stable identity" across re-renders so that React can determine when items are added, removed, or re-ordered. Ideally, keys should correspond to unique and stable identifiers coming from your data, such as `post.id`.
150150

151-
## [Refs](/docs/refs-and-the-dom.html) {#refs}
151+
## [Ref-ek](/docs/refs-and-the-dom.html) {#refs}
152152

153153
React supports a special attribute that you can attach to any component. The `ref` attribute can be an object created by [`React.createRef()` function](/docs/react-api.html#reactcreateref) or a callback function, or a string (in legacy API). When the `ref` attribute is a callback function, the function receives the underlying DOM element or class instance (depending on the type of element) as its argument. This allows you to have direct access to the DOM element or component instance.
154154

155155
Use refs sparingly. If you find yourself often using refs to "make things happen" in your app, consider getting more familiar with [top-down data flow](/docs/lifting-state-up.html).
156156

157-
## [Events](/docs/handling-events.html) {#events}
157+
## [Események](/docs/handling-events.html) {#events}
158158

159159
Handling events with React elements has some syntactic differences:
160160

161161
* React event handlers are named using camelCase, rather than lowercase.
162162
* With JSX you pass a function as the event handler, rather than a string.
163163

164-
## [Reconciliation](/docs/reconciliation.html) {#reconciliation}
164+
## [Összeegyeztetés](/docs/reconciliation.html) {#reconciliation}
165165

166166
When a component's props or state change, React decides whether an actual DOM update is necessary by comparing the newly returned element with the previously rendered one. When they are not equal, React will update the DOM. This process is called "reconciliation".

0 commit comments

Comments
 (0)