-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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.
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
zh-cn: init translation of svelte components #17501
Conversation
Preview URLs Flaws (21)URL:
External URLs (6)URL:
(comment last updated: 2023-12-24 05:29:09) |
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
|
||
这没有硬性规定。有些人更喜欢直观的方法,开始查看标记并在每个似乎具有自己逻辑的组件和子组件周围画框。 | ||
|
||
其他人应用同样用于决定是否创建新函数或对象的技术。其中一种技术是单一职责原则——也就是说,一个组件理想情况下只做一件事。如果它变得越来越庞大,应该将其拆分为更小的子组件。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
其他人应用同样用于决定是否创建新函数或对象的技术。其中一种技术是单一职责原则——也就是说,一个组件理想情况下只做一件事。如果它变得越来越庞大,应该将其拆分为更小的子组件。 | |
其他人应使用同样的技术来决定是否创建新函数或对象。其中一种技术是单一职责原则——也就是说,一个组件理想情况下只做一件事。如果它变得越来越庞大,应该将其拆分为更小的子组件。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, but I can't agree with this recommendation. The original content is "Other people apply the same techniques used for deciding if you should create a new function or object." In my opinion, the "其他人应使用同样的技术来决定是否创建新函数或对象" seems to be more suitable if it is in the article introducing how to create new function or object. @yin1999
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about "其他人借鉴了一些用于创建新函数或对象的技术。"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
Co-authored-by: A1lo <[email protected]>
|
||
这没有硬性规定。有些人更喜欢直观的方法,开始查看标记并在每个似乎具有自己逻辑的组件和子组件周围画框。 | ||
|
||
其他人应用同样用于决定是否创建新函数或对象的技术。其中一种技术是单一职责原则——也就是说,一个组件理想情况下只做一件事。如果它变得越来越庞大,应该将其拆分为更小的子组件。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, but I can't agree with this recommendation. The original content is "Other people apply the same techniques used for deciding if you should create a new function or object." In my opinion, the "其他人应使用同样的技术来决定是否创建新函数或对象" seems to be more suitable if it is in the article introducing how to create new function or object. @yin1999
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
…meworks/svelte_components/index.md
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
…meworks/svelte_components/index.md
One more fix, update the broken links to svelte, please check: mdn/content#31143. |
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Outdated
Show resolved
Hide resolved
...s/zh-cn/learn/tools_and_testing/client-side_javascript_frameworks/svelte_components/index.md
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @hanyujie2002 👍
Description
Same as title
Motivation
Ditto
Additional details
None
Related issues and pull requests
Relates to #16965