Skip to content
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

Use ES6 syntax and babel . #239

Open
sagarpreet-chadha opened this issue Aug 13, 2019 · 9 comments · May be fixed by #240
Open

Use ES6 syntax and babel . #239

sagarpreet-chadha opened this issue Aug 13, 2019 · 9 comments · May be fixed by #240

Comments

@sagarpreet-chadha
Copy link
Collaborator

Let's refactor code to use the ES6 syntax .
Advantages : Less code , more features :)

And ofcourse add babel integration to support all browsers .

@alaxalves
Copy link
Member

YES!!!!

@j-bitmaker
Copy link

Great opportunity!
Can I help you with refactoring?

@sagarpreet-chadha
Copy link
Collaborator Author

Yes i was thinking of starting the work this weekend, but you guys can start early in a branch named refactor_es6 and i can jump in later . Thanks!

@sagarpreet-chadha sagarpreet-chadha linked a pull request Aug 18, 2019 that will close this issue
5 tasks
@deboragaleano
Copy link

Hi, I'm an Outreachy applicant and would like to make my first contribution (all the first-time-only) have been taken already, could I try to work on this one? Thanks!

@mmnoo
Copy link
Contributor

mmnoo commented Nov 25, 2019

Yes please!
@sagarpreet-chadha, what is the status of your work on the feature_es6 branch?
If that work is blocked for whatever reason, could we split this ticket into two? One for updating the code to ES6 and another for just configuring Babel? The latter ticket will allow new work to proceed without having to wait for the rest of the code to update... I'd be happy to work on the Babel ticket. Just let me know, and I will create one. :)

@sagarpreet-chadha
Copy link
Collaborator Author

Hey @mmnoo , i started the work some time ago and there is a PR also for the above.
I remember i was using the arrow functions inside class and there was some problem with "this" pointer.
It was because we cannot use arrow function in leaflet's lifecycle function such as onAdd, onRemove, etc. because we need context's this in those functions.
I figured this out but did not get the time to work on it.
If you want you can make a PR against my PR and start working. Thanks!

@mmnoo
Copy link
Contributor

mmnoo commented Nov 25, 2019

Thanks @sagarpreet-chadha. I started working on my own babel-alone branch this morning, and ran into a bunch of issues with a few of LEL's implied global vars when one looks at the files in the example folder. I'm backing out until I understand LEL a bit more.

@neelesh17
Copy link
Member

Is this issue still open I would like to add this to my Gsoc-2020 project.

@sagarpreet-chadha
Copy link
Collaborator Author

sagarpreet-chadha commented Mar 25, 2020 via email

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 a pull request may close this issue.

6 participants