reactjs / tr.reactjs.org Goto Github PK

I am using memo both on outer component as well as on each of the tab components.

Here is my CommonContainer.tsx:

import { Card, Divider, Grid, Spinner, Tabs, Text } from '@geist-ui/core'
import { memo, useCallback, useState } from 'react'
function CommonContainer(props: Props) {
  return (
    <Card width="100%">
      <Card.Content>
        <Tabs value="p1">
            <Tabs.Item label="P2" value="p2">
              <div >
                <P2QueryTab meta={props.metaList[0]} question={props.question}/>
              </div>
            </Tabs.Item>
            <Tabs.Item label="P1" value="p1">
              <div >
                <P1QueryTab meta={props.metaList[0]} question={props.question}/>
              </div>
            </Tabs.Item>
        </Tabs>
      </Card.Content>
    </Card>
  )
}

export default memo(CommonContainer)

Here is my P2QueryTab.tsx:

import { memo, useEffect, useCallback, useState } from 'react'
import Browser from 'webextension-polyfill'
function P2QueryTab(props: Props) {
  const [answer, setAnswer] = useState<Answer | null>(null)


  useEffect(() => {
    const port = Browser.runtime.connect()
    const listener = (msg: any) => {
      if (msg.text) {
        setAnswer(msg)
      }
    }
    port.onMessage.addListener(listener)
//This postMessage in turn will call external API to get data 
    port.postMessage({ question: props.meta + ' ' + props.question, displayTab: "Insights" })
    return () => {
      port.onMessage.removeListener(listener)
      port.disconnect()
    }
  }, [props.question])


  if (answer) {
    return (
      <div id="answer" dir="auto">
        {answer.text}
      </div>
    )
  }

  return <p className="animate-pulse">Waiting for P2...</p>
}

export default memo(P2QueryTab)

Here is my P1QueryTab.tsx:

import { memo, useEffect, useCallback, useState } from 'react'
import Browser from 'webextension-polyfill'
function P1QueryTab(props: Props) {
  const [answer, setAnswer] = useState<Answer | null>(null)

  useEffect(() => {
    const port = Browser.runtime.connect()
    const listener = (msg: any) => {
      if (msg.text) {
        setAnswer(msg)
      }
    }
    port.onMessage.addListener(listener)
//This postMessage in turn will call external API to get data 
    port.postMessage({
      question: props.meta + ' ' + props.question
    })
    return () => {
      port.onMessage.removeListener(listener)
      port.disconnect()
    }
  }, [props.question])

  if (answer) {
    return (
      <div id="answer" dir="auto">
        {answer.text}
      </div>
    )
  }

  return <p className="animate-pulse">Waiting for P1...</p>
}

export default memo(P1QueryTab)

I have gone through this and this and this and this but still my problem is unsolved.

• most people facing this issue is due to key but I don't have key, I have only 2 props: meta and question which are guaranteed to be same as i visited a tab las time around.
• this answer doesn't rely on memo and does the css trick explicitly himself. Not sure his Typography component uses any memorisation at all. But before going that route I need to understand why don't memo work in my case, why isn't the custom comparator even getting called.
• Some blamed geist-ui tabs so I switched to react-tabs, but result is still the same.

Bir Bakışta Hook'lar bölümünde Effect terimi orjinal haliyle bırakılmışken, Effect Hook'unu Kullanmak bölümünde kimi yerde etki
kimi yerde de efekt olarak çevrilmiş. Hangi terimin kullanılması gerektiğine karar verilmesinin yararlı olacağını düşünüyorum.

Translation for parent is ebeveyn. But this might be confusing and not frequently used. This situation also valid for child translation. You can vote by clicking:
For parent translation:



For child translation:

Slack #tr

Yeni React site react.dev oldu ama bu hala eski .org olana gönderiyor. Bunu tr.react.dev olarak yapmak gerekmiyor mu?

Çeviri Yapmadan Önce Lütfen Aşağıdaki Kuralları Okuyunuz

Çeviri yapma süreci üç adımda gerçekleştirilir:

1. Kontrol listesinde kimsenin işaretlemediği bölümleri seçiniz. Altındaki yorumları kontrol ederek emin olunuz. İpucu: CTRL+F ile istediğiniz bölümle ilgili arama yaparak kontrol edebilirsiniz.

2. Hangi sayfayı çevireceğinizi yorum kısmına yazınız. Lütfen bir seferde birden fazla sayfa almayınız!

3. Projeyi yerel makinenize clone'layınız. Sayfayı çevirdiğinizde commit ederek, pull request gönderiniz.

4. Commit mesajlarini ingilizce yaziniz.

5. Commit mesajlarinda gecmis zaman formu kullanmayiniz. translated tutorial page yerine translate tutorial page. ya da fixed a typo in docs yerine fix a typo in docs.

Tercüme etmeden önce, çeviri kurallarını mutlaka okuyunuz.

İlgili tartışmalara dahil olmak için Slack #tr kanalına katılın.

💡 Repoda Discussions kismi enable edildi. Soru-cevap ya da fikir alisverisi gibi konular icin orayi kullanabiliriz.

Maintainer List

• @alioguzhan
• @serkanisyapan

For New Translators

To translate a page:

1. Check that no one else has claimed your page in the checklist and comments below.
2. Comment below with the name of the page you would like to translate. Please take only one page at a time.
3. Clone this repo, translate your page, and submit a pull request!

Before contributing, read the glossary and style guide (once they exist) to understand how to translate various technical and React-specific terms.

Please be prompt with your translations! If you find that you can't commit anymore, let the maintainers know so they can assign the page to someone else.

For Maintainers

When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Ex:

[x] Home Page (@tesseralis) #12345

When PRs are merged, make sure to mark that page as completed!

Main Content

To do before releasing as an "official" translation. Please translate these pages first.

Note that each section has an index page, which needs to be translated too.

Learn React

• Quick Start (@serkanisyapan) #528

  • Tutorial: Tic Tac Toe (@serkanisyapan) 94ce329
  • Thinking in React (@alioguzhan) #503

• Installation (@yunusemredilber) 373161e

  • Start a New React Project (@bbolek) #401
  • Add React to an Existing Project (@MizginYildirak) #443
  • Editor Setup (@kuntik17) #405
  • React Developer Tools (@kuntik17) #402

• Describing the UI (@TolgaYuceel) #530

  • Your First Component (@serkanisyapan) #509
  • Importing and Exporting Components (@akcoren) #403
  • Writing Markup with JSX (@mervekrblt) #426
  • JavaScript in JSX with Curly Braces (@Cansualtun) #444
  • Passing Props to a Component (@buraksakalli) #416
  • Conditional Rendering (@serkanisyapan) #421
  • Rendering Lists (@serkanisyapan) #410
  • Keeping Components Pure (@MizginYildirak) #418
  • Understanding Your UI as a Tree (@TolgaYuceel ) #532

• Adding Interactivity (@serkanisyapan) #511

  • Responding to Events (@baspinarenes) #413
  • State: A Component's Memory (@agmmnn) #425
  • Render and Commit (@serkanisyapan) #434
  • State as a Snapshot (@emrecanberktas) #468
  • Queueing a Series of State Updates (@serkanisyapan) #447
  • Updating Objects in State (@enesakkose) #445
  • Updating Arrays in State (@serkanisyapan) #460

• Managing State (@serkanisyapan) 5ba09bc

  • Reacting to Input with State (@itsba2) #406
  • Choosing the State Structure (@seckinoter) #457
  • Sharing State Between Components (@cydexx) (@alioguzhan) #438
  • Preserving and Resetting State (@serkanisyapan) #463
  • Extracting State Logic into a Reducer (@agmmnn) #446
  • Passing Data Deeply with Context (@Rogultum) #472
  • Scaling Up with Reducer and Context (@TolgaYuceel) #527

• Escape Hatches (@serkanisyapan)

  • Referencing Values with Refs (@furkanmavili) #455
  • Manipulating the DOM with Refs (@dilarauluturhan) #485
  • Synchronizing with Effects (@serkanisyapan) #505
  • You Might Not Need an Effect (@enesakkose) #469
  • Lifecycle of Reactive Effects (@burakcihan61) #490 #491
  • Separating Events from Effects (@burakcihan61) #493
  • Removing Effect Dependencies (@TolgaYuceel)
  • Reusing Logic with Custom Hooks (@andyanday33)

API Reference

• react: Hooks (@alioguzhan) #504

  • useCallback (@baspinarenes) #470
  • useContext (@osmandlsmn) #423
  • useDebugValue (@buraksakalli) #454
  • useDeferredValue (@baspinarenes) #462
  • useEffect (@serkanisyapan) #471
  • useId (@baspinarenes) #415
  • useImperativeHandle (@buraksakalli) #456
  • useInsertionEffect (@enesakkose) #459
  • useLayoutEffect (@baspinarenes) #420
  • useMemo (@iefendiev) #451
  • useReducer (@buraksakalli) #428
  • useRef (@coskuncakir) #407
  • useState (@serkanisyapan) #508
  • useSyncExternalStore (@baspinarenes) #452
  • useTransition (@halilatilla) #450

• react: Components

  • <Fragment> (<>) (@K2adir) #419
  • <Profiler> (@agmmnn) #431
  • <StrictMode> (@hasancankucuk) #482
  • <Suspense> (@andyanday33) #440

• react: APIs (@baspinarenes) #453

  • createContext (@halilatilla) #409
  • forwardRef (@halilatilla) #427
  • lazy (@baspinarenes) #422
  • memo (@baspinarenes) #436
  • startTransition (@halilatilla) #442

• react-dom: Components (@agmmnn) #430

  • Common (e.g. <div>) (@itsba2) #519
  • <input> (@hasancankucuk) #481
  • <option> (@K2adir) #435
  • <progress> (@agmmnn) #429
  • <select> (@serkanisyapan) #466
  • <textarea> (@hasancankucuk) #479

• react-dom: APIs (@agmmnn) #431

  • createPortal (@arif-ozberk) #483
  • flushSync (@K2adir) #448
  • findDOMNode (@enesthedev) #496
  • hydrate (@ctnkaan)
  • render (@buraksakalli) #465
  • unmountComponentAtNode (@ctnkaan) #536

• react-dom/client: Client APIs (@altankurt) #424

  • createRoot (@alpererdogan8) #523
  • hydrateRoot

• react-dom/server: Server APIs (@andyanday33) #439

  • renderToNodeStream
  • renderToPipeableStream (@hasancankucuk) #487
  • renderToReadableStream
  • renderToStaticMarkup
  • renderToStaticNodeStream (@arif-ozberk) #473
  • renderToString (@arif-ozberk) #480

Navigation and UI

We suggest to leave most of the UI translation until the end. We plan to do some invasive changes to the website folder layout and components, so postponing this until your translation is almost complete would make it easier to merge the changes from our side later. It might make sense to translate the homepage above the fold early, but leave the rest for later. As individual pages get translated, you can change the page titles in the corresponding sidebar files. Finally, when you're translating the navigation, make sure to test both desktop and mobile layouts.

• Homepage (currently in HomeContent.js) (@turkerdev) #404
• Sidebars (currently in src/sidebar*.json)
• Top-level navigation (currently in TopNav.tsx) (@alioguzhan) #504

When You're Ready...

After everything above is translated, add your language to deployedLanguages in Seo.tsx of the original reactjs/react.dev repository.

Secondary Content

These API pages should ideally be translated too, but they're less urgent and can be done after the others:

• Legacy React APIs
  • Children
  • cloneElement
  • Component
  • createElement
  • createFactory
  • createRef
  • isValidElement
  • PureComponent

Optional Content

These aren't the main translation targets, but if you'd like to do them, feel free to expand the list to include their subpages:

• Community (@coderdal) #477
• Blog
• Warnings

Çeviri Yapmadan Önce Lütfen Aşağıdaki Kuralları Okuyunuz

Çeviri yapma süreci üç adımda gerçekleştirilir:

1. Kontrol listesinde kimsenin işaretlemediği bölümleri seçiniz. Altındaki yorumları kontrol ederek emin olunuz. İpucu: CTRL+F ile istediğiniz bölümle ilgili arama yaparak kontrol edebilirsiniz.

2. Hangi sayfayı çevireceğinizi yorum kısmına yazınız. Lütfen bir seferde birden fazla sayfa almayınız!

3. Projeyi yerel makinenize clone'layınız. Sayfayı çevirdiğinizde commit ederek, pull request gönderiniz.

4. Commit mesajlarini ingilizce yaziniz.

5. Commit mesajlarinda gecmis zaman formu kullanmayiniz. translated tutorial page yerine translate tutorial page. ya da fixed a typo in docs yerine fix a typo in docs.

Tercüme etmeden önce, çeviri kurallarını mutlaka okuyunuz.

İlgili tartışmalara dahil olmak için Slack #tr kanalına katılın.

Maintainer List

• @alioguzhan
• @yunusemredilber

For New Translators

To translate a page:

1. Check that no one else has claimed your page in the checklist and comments below.
2. Comment below with the name of the page you would like to translate. Please take only one page at a time.
3. Clone this repo, translate your page, and submit a pull request!

Before contributing, read the glossary and style guide (once they exist) to understand how to translate various technical and React-specific terms.

Please be prompt with your translations! If you find that you can't commit anymore, let the maintainers know so they can assign the page to someone else.

For Maintainers

When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Ex:

• Home Page (@tesseralis) #1

When PRs are merged, make sure to mark that page as completed!

Core Pages

To do before releasing as an "official" translation. Please translate these pages first.

• Home Page (@helloanil) #2
• Tutorial (@ozcanzaferayan) #3

Basics

• Hello World (@enestufekci) #8
• Introducing JSX (@ozcanzaferayan) #65
• Rendering Elements (@ozcanzaferayan) #12
• Components and Props (@ozcanzaferayan) #14
• State and Lifecycle (@ozcanzaferayan) #15
• Handling Events (@ozcanzaferayan) #29
• Conditional Rendering (@alperen)
• Lists and Keys (@alioguzhan) #22
• Forms (@aykutkardas) #16
• Lifting State Up (@Poseid10ur) #19
• Composition vs Inheritance (@omergulcicek) #51
• Thinking in React (@alioguzhan) #34

API Reference

• React (@ahmett) #70
• React.Component() (@ozcanzaferayan) #32
• ReactDOM (@ekocibar ) #40
• ReactDOMServer (@alioguzhan) #67
• DOM Elements (@Poseid10ur) #28
• SyntheticEvent (@helloanil) #36
• Test Utilities (@Poseid10ur) #37
• Shallow Renderer (@suyalcinkaya) #71
• Test Renderer (@erinc35) #42
• JS Environment Requirements (@ebrugulec) #41
• Glossary (@suyalcinkaya) #53

Navigation

These are the navigation links that appear in the sidebar. Possibly wait until
the corresponding sections are translated to do these.

• tutorial/nav.yml (@theilgazcode) #60
• docs/nav.yml (@alperen) #86

Next Steps

These are the next most important translations, ordered by importance:

Installation

• Getting Started (@mahmutkaya) #26
• Add React to a Website (@mahmutkaya) #26
• Create a New React App (@mertcb) (@mertoguz) #63
• CDN Links (@mahmutkaya) #26
• Release Channels content/docs/release-channels.md (@eminaydin) #211

Hooks

Everyone is hooked on hooks! People are really excited for these and it would be great for them to be translated.

• Introducing Hooks (@suyalcinkaya) #93
• Hooks at a Glance (@hbarang) #161
• Using the State Hook (@hakanbakacak) #107
• Using the Effect Hook (@EngincanV) #245
• Rules of Hooks (@suyalcinkaya) (#54)
• Building Your Own Hooks (@ozcanzaferayan) (#91)
• Hooks API Reference (@sametweb) (#266)
• Hooks FAQ

Concurrent Mode (New)

• Adopting Concurrent Mode content/docs/concurrent-mode-adoption.md (@aakay) (#202)
• Introducing Concurrent Mode content/docs/concurrent-mode-intro.md (@ataberkgrl ) (#253)
• Concurrent UI Patterns content/docs/concurrent-mode-patterns.md
• Concurrent Mode API Reference content/docs/concurrent-mode-reference.md (@ahmett) (#210)
• Suspense for Data Fetching content/docs/concurrent-mode-suspense.md

Warnings

These are the pages that you get when you click the links in the console (e.g. https://reactjs.org/warnings/dont-call-proptypes.html). People tend to search these, so please don't translate the error message itself.

• dont-call-proptypes (@muratdogan17) #84
• invalid-aria-prop (@suyalcinkaya) (#55)
• invalid-hook-call-warning (@emrekara37) #144
• legacy-factories (@muratdogan17) #85
• refs-must-have-owner (@muratdogan17) #89
• special-props (@suyalcinkaya) (#56)
• unknown-prop (@alioguzhan) ) (#295)

Advanced Guides

• Accessibility (@fatmabadri) #279
• Code-Splitting (@mustaphaturhan) #44
• Context (@metinsut) #108
• Error Boundaries (@aakay) #109
• Forwarding Refs (@ngTurk) #222
• Fragments (@ebrugulec) #81
• Higher-Order Components (@hbarang) #159
• Integrating with Other Libraries (@fatmabadri) #272
• JSX In Depth (@yunusemredilber) #212
• Optimizing Performance
• Portals #98 (@ahmett)
• React Without ES6 (@mustaphaturhan) #48
• React Without JSX (@ahmett) #47
• Reconciliation (@yunusemredilber) #207
• Refs and the DOM (@SafaElmali) #83
• Render Props (@hbarang) #153
• Static Type Checking (@aakay) #105
• Strict Mode (@metinogurlu) #209
• Typechecking With PropTypes (@ahmett) (#50)
• Uncontrolled Components (@ahmett) (#66)
• Web Components (@suyalcinkaya) (#59)

FAQ

• AJAX and APIs (@emreyalvac) #18
• Babel, JSX, and Build Steps (@suyalcinkaya) (#68)
• Passing Functions to Components (@umutcanbolat) #111
• Component State (@suyalcinkaya) #94
• Styling and CSS (@yunusemredilber) #208
• File Structure (@umutcanbolat) #99
• Versioning Policy (@Oedipus) #103
• Virtual DOM and Internals (@suyalcinkaya) #97

Contributing

Priority: Low

• How to Contribute
• Codebase Overview
• Implementation Notes
• Design Principles

Components

Components in src/components that have some text in them.

• CodeEditor (@alioguzhan) #78
• CodeExample (@alioguzhan) #77
• ErrorDecoder (@alioguzhan) #79
• LayoutFooter (@alioguzhan) #73
• LayoutHeader (@alioguzhan) #73
• MarkdownPage (@alioguzhan) #76

Additional Translations

These are not the primary translation targets.

• Blog
• Community (@reincore) #123

We need to decide this to make it standard and consistent. An example of usage:

A Component Using External Plugins

1. Harici Eklentiler Kullanan Bir Bileşen
2. Dış Eklentiler Kullanan Bir Bileşen

Internal state data

1. Dahili State Verisi
2. İç State Verisi

Internal:

External:

Congrats on almost finishing the translation of the Turkish docs! There are just a couple more things we need to do before we can mark the core pages as complete!

• Change the [DocSearch API key] #69 (https://github.com/reactjs/es.reactjs.org/blob/ed07fa53dc9ab7950e630900f7da3a7c821d63a6/src/components/LayoutHeader/DocSearch.js#L25). One of the maintainers needs to sign up for DocSearch
• Go over the pages of the site one last time to check for consistency #88