Rescreva essa parte da string com as seguintes condições: 1. Não elimine NENHUMA…
- User
Rescreva essa parte da string com as seguintes condições: 1. Não elimine NENHUMA informação dada no artigo. 2. Termos, variáveis, expressões ou referências devem ser SEMPRE mantidos em inglês. 3. Apenas transcreva o artigo para um inglês mais simples, tornando ele mais literal e direto, sem alterar o contexto. 4. Não remova as tags HTML e nem os "#thedivisor#". 5. Você deve me enviar sua resposta em texto puro, sem markdown.
#thedivisor#Sometimes, passing props gets very repetitive:#thedivisor#There’s nothing wrong with repetitive code—it can be more legible. But at times you may value conciseness. Some components forward all of their props to their children, like how this <code dir="ltr" class="inline text-code text-secondary dark:text-secondary-dark px-1 rounded-md no-underline bg-gray-30 bg-opacity-10 py-px">Profile</code> does with <code dir="ltr" class="inline text-code text-secondary dark:text-secondary-dark px-1 rounded-md no-underline bg-gray-30 bg-opacity-10 py-px">Avatar</code>. Because they don’t use any of their props directly, it can make sense to use a more concise “spread” syntax:#thedivisor#This forwards all of <code dir="ltr" class="inline text-code text-secondary dark:text-secondary-dark px-1 rounded-md no-underline bg-gray-30 bg-opacity-10 py-px">Profile</code>’s props to the <code dir="ltr" class="inline text-code text-secondary dark:text-secondary-dark px-1 rounded-md no-underline bg-gray-30 bg-opacity-10 py-px">Avatar</code> without listing each of their names.#thedivisor#<strong class="font-bold">Use spread syntax with restraint.</strong> If you’re using it in every other component, something is wrong. Often, it indicates that you should split your components and pass children as JSX. More on that next!#thedivisor#It is common to nest built-in browser tags:#thedivisor#Sometimes you’ll want to nest your own components the same way:#thedivisor#When you nest content inside a JSX tag, the parent component will receive that content in a prop called <code dir="ltr" class="inline text-code text-secondary dark:text-secondary-dark px-1 rounded-md no-underline bg-gray-30 bg-opacity-10 py-px">children</code>. For example, the <code dir="ltr" class="inline text-code text-secondary dark:text-secondary-dark px-1 rounded-md no-underline bg-gray-30 bg-opacity-10 py-px">Card</code> component below will receive a <code dir="ltr" class="inline text-code text-secondary dark:text-secondary-dark px-1 rounded-md no-underline bg-gray-30 bg-opacity-10 py-px">children</code> prop set to <code dir="ltr" class="inline text-code text-secondary dark:text-secondary-dark px-1 rounded-md no-underline bg-gray-30 bg-opacity-10 py-px"><Avatar /></code> and render it in a wrapper div:#thedivisor#Try replacing the <code dir="ltr" class="inline text-code text-secondary dark:text-secondary-dark px-1 rounded-md no-underline bg-gray-30 bg-opacity-10 py-px"><Avatar></code> inside <code dir="ltr" class="inline text-code text-secondary dark:text-secondary-dark px-1 rounded-md no-underline bg-gray-30 bg-opacity-10 py-px"><Card></code> with some text to see how the <code dir="ltr" class="inline text-code text-secondary dark:text-secondary-dark px-1 rounded-md no-underline bg-gray-30 bg-opacity-10 py-px">Card</code> component can wrap any nested content. It doesn’t need to “know” what’s being rendered inside of it. You will see this flexible pattern in many places.#thedivisor#You can think of a component with a <code dir="ltr" class="inline text-code text-secondary dark:text-secondary-dark px-1 rounded-md no-underline bg-gray-30 bg-opacity-10 py-px">children</code> prop as having a “hole” that can be “filled in” by its parent components with arbitrary JSX. You will often use the <code dir="ltr" class="inline text-code text-secondary dark:text-secondary-dark px-1 rounded-md no-underline bg-gray-30 bg-opacity-10 py-px">children</code> prop for visual wrappers: panels, grids, etc.#thedivisor#<cite>Illustrated by<!-- --> <a target="_blank" rel="noreferrer" class="text-link dark:text-link-dark" href="https://nearestnabors.com/">Rachel Lee Nabors</a></cite> - Assistant
#thedivisor#Sometimes, passing props can be very repetitive:#thedivisor#There is nothing wrong with repetitive code—it can be clearer. But sometimes you might prefer to be more concise. Some components pass all their props to their children, like how this Profile does with Avatar. Because they do not use any of their props directly, it can be better to use a shorter “spread” syntax:#thedivisor#This sends all of Profile’s props to the Avatar without needing to list each of their names.#thedivisor#Use spread syntax carefully. If you are using it in every other component, something is not right. Often, it means you should break your components apart and pass children as JSX. More on that coming up!#thedivisor#It is common to nest built-in browser tags:#thedivisor#Sometimes you will want to nest your own components in the same way:#thedivisor#When you put content inside a JSX tag, the parent component gets that content in a prop called children. For example, the Card component below will get a children prop set to <Avatar /> and will render it in a wrapper div:#thedivisor#Try changing the <Avatar> inside <Card> with some text to see how the Card component can wrap any nested content. It doesn’t need to “know” what is being rendered inside it. You will find this flexible pattern in many places.#thedivisor#You can think of a component with a children prop as having a “hole” that can be “filled in” by its parent components with any JSX. You will often use the children prop for visual wrappers: panels, grids, etc.#thedivisor#Illustrated by Rachel Lee Nabors
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.