Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Sync with upstream @ 035c5267#14

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Closed
javascript-translate-bot wants to merge209 commits intomasterfromsync-035c5267

Conversation

javascript-translate-bot

This PR was automatically generated to merge changes fromen.javascript.info at035c526

Conflicted files in this PR have labels ">>>..." with both sides of conflict. If you merge this PR, you'll need to examine the listed files and resolve conflicts.

Alternatively, you can close this PR and merge conflicting changes manually.

The following files have conflicts and may need updates of the translations:

To merge changes manually (instead of merging this PR):

  1. Add remote upstream that links to the English version (only needs to be done once)
    • git add remote upstream https://github.com/javascript-tutorial/en.javascript.info
  2. Commit all current work locally andgit checkout master
  3. Pull the recent changes from the English version:
    • git pull upstream master
  4. Deal with the conflicts. If a conflict touches a few lines, then just fix it. Otherwise, following commands can help:
    • Checkout your (translated) version of a file/folder at the given path (removes all upstream changes):
      • git checkout --ours <path>
    • See the diff, what changed in the upstream file since branches diverged:
      • git diff --word-diff master...upstream/master <path> (please note: three dots in the command)
    • Then you can examine the changes in upstream and add them manually
  5. When conflicts resolved, commit them andgit push origin master

This PR will be closed and replaced with a new one in a few days.

wdscxsjand others added30 commitsOctober 3, 2022 16:58
Same as title
The event type for `onerror()` is a vanilla `Event` that has no `message` property (or anything interesting about the error). Further info from this StackOverflow question: [Javascript doesn't catch error in WebSocket instantiation](https://stackoverflow.com/questions/31002592/javascript-doesnt-catch-error-in-websocket-instantiation/31003057#31003057).
smith558and others added29 commitsJuly 10, 2024 16:21
Fixing a minor grammatical typo in the document.
The code uses the function named 'askPassword' but the text above it explaining the error reason says 'ask' instead of 'askPassword'
minor fix to function name written in explanation
Suggested edit - to make the phrase clearer.
the comment number is missing when the we mention line 2
Correction of grammatical error
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

54 participants
@javascript-translate-bot@wdscxsj@joaquinelio@aki-mizu@TevaHenry@Rnbsov@iliakan@adam4nj@f6p@Vic-Bonlight@leviding@nikolai-chernolutskii@Alexandre887@alagunoff@cerealexperiments@bogdanbacosca@orelby@a-v-gor@Violet-Bora-Lee@sagarpanchal@odsantos@MAHIN0093@marcusicaro@JeraldVin@Raviikumar001@pradeep-ramola@MSHNK1@rahulrao0209@WOLFRIEND@smith558@nakhodkin@JaFro96@alexandermirzoyan@CJDumbleton@qadzek@mikayel00@eedrxs@nepikn@0xtpsl@Filin3@ellie-heidari@pvepamb1@sneeed@kricsleo@FloffyGarlic@shallow-beach@tonybishnoi@nikoandpiko@zakingslayerv22@pj-szdm@mhi1627@AdityaGirdhar@Gleb-Pastushenko@vincent-clipet

[8]ページ先頭

©2009-2025 Movatter.jp