Skip to content

Update handling-text-input.md #984

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: production
Choose a base branch
from
Open

Update handling-text-input.md #984

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion cndocs/handling-text-input.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ title: 处理文本输入

[`TextInput`](textinput#content)是一个允许用户输入文本的[基础组件](intro-react-native-components)。它有一个名为`onChangeText`的属性，此属性接受一个函数，而此函数会在文本变化时被调用。另外还有一个名为`onSubmitEditing`的属性，会在文本被提交后（用户按下软键盘上的提交键）调用。

假如我们要实现当用户输入时，实时将其以单词为单位翻译为另一种文字。我们假设这另一种文字来自某个吃货星球，只有一个单词： 🍕。所以"Hello there Bob"将会被翻译为"🍕🍕🍕"。
假如我们要实现当用户输入时，实时将其以单词为单位翻译为另一种文字。我们假设这另一种文字来自某个吃货星球，只有一个单词： 🍕。所以"Hello there Bob"将会被翻译为"🍕🍕🍕🍕🍕🍕"。
Copy link

@coderabbitai coderabbitai bot Nov 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Critical: Documentation and code logic are inconsistent.

Line 8 now claims that "Hello there Bob" translates to "🍕🍕🍕🍕🍕🍕" (6 emojis), but the code on line 25 generates only 1 emoji per word, resulting in "🍕 🍕 🍕" (3 emojis).

The documentation update was not accompanied by a corresponding code change. The example code still uses:

{text.split(' ').map((word) => word && '🍕').join(' ')}

This produces one emoji per word, not six emojis per word.

Please choose one of the following approaches to fix this inconsistency:

  1. Revert the documentation to match the actual code behavior:

    -假如我们要实现当用户输入时，实时将其以单词为单位翻译为另一种文字。我们假设这另一种文字来自某个吃货星球，只有一个单词： 🍕。所以"Hello there Bob"将会被翻译为"🍕🍕🍕🍕🍕🍕"。
+假如我们要实现当用户输入时，实时将其以单词为单位翻译为另一种文字。我们假设这另一种文字来自某个吃货星球，只有一个单词： 🍕。所以"Hello there Bob"将会被翻译为"🍕 🍕 🍕"。

  2. Update the code to produce 6 emojis per word (if that was the intended behavior):

    -        {text.split(' ').map((word) => word && '🍕').join(' ')}
+        {text.split(' ').map((word) => word && '🍕🍕🍕🍕🍕🍕').join(' ')}

Also applies to: 25-25

🏁 Script executed:

#!/bin/bash
# Verify the file exists and extract lines 8 and 25 with context
if [ -f "cndocs/handling-text-input.md" ]; then
  echo "=== File exists ==="
  echo ""
  echo "=== Line 8 (with 3 lines before and after) ==="
  sed -n '5,11p' cndocs/handling-text-input.md
  echo ""
  echo "=== Line 25 (with 5 lines before and after) ==="
  sed -n '20,30p' cndocs/handling-text-input.md
else
  echo "File cndocs/handling-text-input.md does not exist"
  echo "Searching for similar files..."
  find . -name "*handling-text*" -o -name "*input*" 2>/dev/null | grep -E "\.(md|markdown)$" | head -20
fi

Length of output: 1109

🏁 Script executed:

#!/bin/bash
# Search for handling-text-input.md outside archived directories
echo "=== Searching for handling-text-input.md (excluding archived) ==="
find . -path './git/archived_docs' -prune -o -name "handling-text-input.md" -type f -print

echo ""
echo "=== Checking if cndocs directory exists ==="
if [ -d "cndocs" ]; then
  ls -la cndocs/ | head -20
else
  echo "cndocs directory does not exist"
fi

echo ""
echo "=== Checking for docs directories ==="
find . -path './git/archived_docs' -prune -o -type d -name "docs" -o -name "*docs*" -print | grep -v archived | head -20

Length of output: 4364

🏁 Script executed:

#!/bin/bash
# Extract lines 8 and 25 with context from cndocs/handling-text-input.md
echo "=== Line 8 context (lines 5-12) ==="
sed -n '5,12p' cndocs/handling-text-input.md
echo ""
echo "=== Line 25 context (lines 20-32) ==="
sed -n '20,32p' cndocs/handling-text-input.md
echo ""
echo "=== Full file overview (first 40 lines) ==="
head -40 cndocs/handling-text-input.md

Length of output: 2175

Critical: Documentation and code logic are inconsistent.

Line 8 claims that "Hello there Bob" translates to "🍕🍕🍕🍕🍕🍕" (6 emojis), but the code on line 25 generates only 1 emoji per word, resulting in "🍕 🍕 🍕" (3 emojis).

The code at line 25—{text.split(' ').map((word) => word && '🍕').join(' ')}—splits the input into 3 words and maps one emoji to each, producing 3 emojis total, not 6.

Fix this inconsistency by choosing one approach:

  1. Revert documentation to match code behavior: Update line 8 to claim output is "🍕 🍕 🍕" instead of "🍕🍕🍕🍕🍕🍕"

  2. Update code to produce 6 emojis per word: Change line 25 to map each word to '🍕🍕🍕🍕🍕🍕'

🤖 Prompt for AI Agents 
In cndocs/handling-text-input.md around lines 8 and 25, the example output
("Hello there Bob" → "🍕🍕🍕🍕🍕🍕") conflicts with the component code that
produces one pizza emoji per word ("🍕 🍕 🍕"); either update line 8 to match
the code and show "🍕 🍕 🍕" (add spaces between emojis) or change the code at
line 25 so each mapped word returns six pizza emojis (and ensure join spacing is
handled as desired); pick one approach and make the corresponding edit so
documentation and code are consistent.


```SnackPlayer name=Handling%20Text%20Input
import React, { useState } from 'react';
Expand Down