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

Rewrite in ES7 #223

Open
cybertk opened this issue Aug 4, 2017 · 12 comments
Open

Rewrite in ES7 #223

cybertk opened this issue Aug 4, 2017 · 12 comments

Comments

@cybertk
Copy link
Owner

cybertk commented Aug 4, 2017

As ES7 brings most of Coffee Script features, it's time to roll it.

@oshalygin
Copy link
Collaborator

oshalygin commented Aug 7, 2017

Let's get started gents, strategy for this? I'm proposing a feature branch as we start committing against it and making sure things are working. That gives us the ability to keep the master branch clean in case there are critical updates we have to make and still be able to push to npm.

pruposed branch: es7-migration.

@cybertk
Copy link
Owner Author

cybertk commented Aug 7, 2017

Good to go

@oshalygin
Copy link
Collaborator

I'll push the branch and start some of the initial work. There are a couple of things to figure out, I'll create issues for each one for discussion so that we can move efficiently.

@sichvoge
Copy link

sichvoge commented Sep 5, 2017

@oshalygin should we add a milestone for that so that we can see the progress?

@oshalygin
Copy link
Collaborator

@sichvoge yeah lets do it. I've been on vacation in Seattle for two weeks and just got back, I'm going to get rolling again on this project.

@sichvoge
Copy link

sichvoge commented Sep 8, 2017

Cool, btw - we should probably sit down at some point and talk about the current parser and what we (RAML Workgroup) are doing around the API Modeling Framework.

In short, we will replace our current parsers with that as it provides a more formal description of the actual parsed model with well defined programmatic interfaces. It will simplify a lot.

What that actually means, we could talk over Hangout or Zoom. What do you think?

It should still not stop us to go the first step on migrating the current implementation to ES7.

@oshalygin
Copy link
Collaborator

I'm down. Do we want to start this over Gitter/Slack? Sorry I've been bad about responding

@sichvoge
Copy link

I can add you to a Slack if you like. I am back in action on Monday as I am currently relocating!

@oshalygin
Copy link
Collaborator

Awesome !! Don't break your back 📦

@sichvoge
Copy link

Can you guys send me an email to christian (dot) vogel (at) mulesoft (dot) com. Need your email address to add you.

@shumsky
Copy link

shumsky commented Jan 22, 2018

Hi guys,

Is this issue still relevant? Does the branch es7-migration contain the latest work on this?

@plroebuck
Copy link
Collaborator

@shumsky Sorry for late reply. Had nothing to do with this branch, but from what I can tell it looks like it was branched and the README modified -- so I'd say not...

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

No branches or pull requests

5 participants