Skip to content

Sync with upstream @ ff152b12 #68

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

Closed
wants to merge 227 commits into from
Closed

Conversation

javascript-translate-bot

This PR was automatically generated to merge changes from en.javascript.info at ff152b1

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 and git 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 and git push origin master

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

paroche and others added 30 commits February 6, 2020 23:36
My proposed change may not be right, but "make a request to URL" was unclear, and it's `fetch` that's used below to make the request. If 'request to URL' has some special meaning and is what you want to say, maybe some rephrasing is in order.
Fixing a typo
without -> with
minor type fixes
minor typo fix
There are some missing "=" sign according to the question.
2 small fixes
The title makes me ask "is 'if' keyword operator or not?".
I think 'if' is not operator because it does not return any value and it is called if-statement.
Used "unitialized" instead of "uninitialized"
There are also array literals and string literals.
Minor edit around example code: " should be around id
Move comma before square bracket
Object.create(proto[, descriptors])
Revision to unary plus not allowed bigints description in response to PR
MuhammedZakir and others added 26 commits September 10, 2020 14:42
Restructure the Solution for 'Army of Functions' task and Fix Typos
Fix javascript-tutorial#2090 - Spelling Mistake
Close javascript-tutorial#2079 - Remove 'elem' from `elem.scrollLeft/scrollTop`
Fix javascript-tutorial#2098 - replace let with var in IIFE example
Improve 'long polling' article. Complements #2073.
Corrected spelling of "representation"
Sync safe Number borders across chapter 1.2.5
@javascript-translate-bot javascript-translate-bot added the review needed Review needed, please approve or request changes label Sep 14, 2020
@javascript-translate-bot javascript-translate-bot requested a review from a team September 14, 2020 05:02
@CLAassistant
Copy link

CLAassistant commented Sep 14, 2020

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 3 committers have signed the CLA.

✅ iliakan
❌ apcurran
❌ MuhammedZakir
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
review needed Review needed, please approve or request changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.