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

Document transitioning from JSCS to ESLint #5859

Closed
nzakas opened this Issue Apr 14, 2016 · 4 comments

Comments

@nzakas
Member

nzakas commented Apr 14, 2016

Once we have figured out all of the technical details to allow people to transition from JSCS to ESLint, we will need to document the process. My guess is that we'll need some documentation for transitioning both from JSCS 2.x and 3.x. The things we should cover:

  1. How to convert .jscsrc into .eslintrc
  2. The shareable configs that are the equivalent of JSCS presets
  3. Any manual changes that need to be done in order to complete the conversion
  4. An overview of how the user experience is different
  5. Where to go for questions

This will clearly have to come last, just don't want to forget. :)

@nzakas nzakas added this to the JSCS Compatibility milestone Apr 14, 2016

@markelog markelog referenced this issue Aug 12, 2016

Closed

Identify most popular presets for JSCS #5858

8 of 10 tasks complete

@nzakas nzakas self-assigned this Aug 19, 2016

nzakas added a commit that referenced this issue Aug 19, 2016

nzakas added a commit that referenced this issue Aug 24, 2016

nzakas added a commit that referenced this issue Aug 25, 2016

@Aladdin-ADD

This comment has been minimized.

Show comment
Hide comment
@Aladdin-ADD

Aladdin-ADD Jul 5, 2017

Member

seems it can be closed -- #6942 was merged.

Member

Aladdin-ADD commented Jul 5, 2017

seems it can be closed -- #6942 was merged.

@platinumazure

This comment has been minimized.

Show comment
Hide comment
@platinumazure

platinumazure Jul 5, 2017

Member

@Aladdin-ADD Looks like nzakas intentionally changed the commit to "ref" this issue instead of "fix" (close) it. So maybe nzakas thinks they're more to do. Unfortunately, with nzakas out of commission, we won't know for sure.

@eslint/eslint-tsc Any thoughts on whether we have anything to do here? Or should we close this?

Member

platinumazure commented Jul 5, 2017

@Aladdin-ADD Looks like nzakas intentionally changed the commit to "ref" this issue instead of "fix" (close) it. So maybe nzakas thinks they're more to do. Unfortunately, with nzakas out of commission, we won't know for sure.

@eslint/eslint-tsc Any thoughts on whether we have anything to do here? Or should we close this?

@not-an-aardvark

This comment has been minimized.

Show comment
Hide comment
@not-an-aardvark

not-an-aardvark Jul 5, 2017

Member

Based on #6942 (comment), my guess is that it was changed to "refs" because there is some more work to do with the guide. However, I'm unsure what that work is. If we're not sure about specific action items, I think we can close this and possibly improve the guide later.

Member

not-an-aardvark commented Jul 5, 2017

Based on #6942 (comment), my guess is that it was changed to "refs" because there is some more work to do with the guide. However, I'm unsure what that work is. If we're not sure about specific action items, I think we can close this and possibly improve the guide later.

@not-an-aardvark

This comment has been minimized.

Show comment
Hide comment
@not-an-aardvark

not-an-aardvark Sep 3, 2017

Member

Closing this issue since no one has proposed any future work on it.

Member

not-an-aardvark commented Sep 3, 2017

Closing this issue since no one has proposed any future work on it.

@not-an-aardvark not-an-aardvark moved this from In Progress to Done in JSCS Compatibility Sep 3, 2017

@eslint eslint bot locked and limited conversation to collaborators Mar 3, 2018

@eslint eslint bot added the archived due to age label Mar 3, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.