Skip to content

Substituted var with let/const; new lesson scope-2 - #214

Closed
huberv wants to merge 5 commits into
workshopper:masterfrom
huberv:master
Closed

Substituted var with let/const; new lesson scope-2#214
huberv wants to merge 5 commits into
workshopper:masterfrom
huberv:master

Conversation

@huberv

@huberv huberv commented Nov 21, 2017

Copy link
Copy Markdown

Hi all,
I modernized the lessons somewhat:

  • Substituted the var keyword with const/let. Newcomers should learn the modern stuff right from the start.
  • Adapted the description of the variable lesson (Enlish version only).
  • Added new lesson scope-2 (English only).
  • Adapted text of lesson scope (now sets the stage to the new lesson scope-2) (English only).

I'd be glad if you would incorporate the changes in order to allow newbees to use a modern JavaScript style right from the start.

Unfortunately I'm not aware of how the process for triggering translations of the other currently supported languages is. Please advise on this topic.

Substituted the var keyword with const/let. Newcomers should learn the modern stuff right from the start.
Adapted the description of the variable lesson (Enlish version only).
Added new lesson scope-2 (English only).
Adapted text of lesson scope (now sets the stage to the new lesson scope-2) (English only).
@AnshulMalik

Copy link
Copy Markdown
Contributor

Hey @huberv This is great!
This PR contains lots of changes, it'd be great if we can create separate PRs for smaller changes :)

@huberv

huberv commented Oct 31, 2018

Copy link
Copy Markdown
Author

Hi @AnshulMalik, that's definitely true, but from my point of view it doesn't make sense to split up the change from "var" to "const" or "let" into different pull requests => you'd have to accept all of them in order to get a consistent update.

I know the changes are in lots of files, but each individual change is quite small...

@SomeoneWeird SomeoneWeird left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I'm happy to merge this rather than splitting it into multiple PRs. If it was any other change I would recommend splitting it up, but this is easy to review and won't break anything.

@AnshulMalik

Copy link
Copy Markdown
Contributor

Looks like it needs a rebase, then we are good to go. @huberv

Comment thread problems/scope/problem.md Outdated
@huberv

huberv commented Nov 2, 2018

Copy link
Copy Markdown
Author

@AnshulMalik Thanks for the review! I fixed the typo you found and updated the pull request according to the procedure described here: https://help.github.com/articles/syncing-a-fork/ (I'm not in love with rebasing repos).
Please double-check again.

@lupomontero

Copy link
Copy Markdown
Contributor

Hi there, any news with regards to this PR? I think it would make a lot of sense to include these changes and start introducing more modern features. Anything I can do to help?

@itzsaga

itzsaga commented Jun 29, 2019

Copy link
Copy Markdown
Member

@lupomontero well, currently there's a conflict on this PR. So resolving that would be a first step.

@huberv

huberv commented Jul 1, 2019

Copy link
Copy Markdown
Author

@lupomontero @itzsaga
Hi! I just resolved the conflict.

I'd appreciate if my pull request would finally make it into the master.

Because the pull request has been waiting for quite some time I suggest that somebody pulls from the master to my pull request, does a code review and then merges the pull request into the master.

@ledsun

ledsun commented Aug 17, 2019

Copy link
Copy Markdown
Collaborator

#265 is the same change as this PR.

@ledsun ledsun closed this Aug 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants