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

Document transitioning from JSCS to ESLint #5859

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

Document transitioning from JSCS to ESLint #5859

nzakas opened this issue Apr 14, 2016 · 4 comments
Assignees
Labels
accepted There is consensus among the team that this change meets the criteria for inclusion archived due to age This issue has been archived; please open a new issue for any further discussion documentation Relates to ESLint's documentation enhancement This change enhances an existing feature of ESLint

Comments

@nzakas
Copy link
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 enhancement This change enhances an existing feature of ESLint documentation Relates to ESLint's documentation accepted There is consensus among the team that this change meets the criteria for inclusion labels Apr 14, 2016
@nzakas nzakas added this to the JSCS Compatibility milestone Apr 14, 2016
@nzakas nzakas self-assigned this Aug 19, 2016
@aladdin-add
Copy link
Member

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

@platinumazure
Copy link
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?

@not-an-aardvark
Copy link
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.

@not-an-aardvark
Copy link
Member

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-deprecated eslint-deprecated bot locked and limited conversation to collaborators Mar 3, 2018
@eslint-deprecated eslint-deprecated bot added the archived due to age This issue has been archived; please open a new issue for any further discussion label Mar 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
accepted There is consensus among the team that this change meets the criteria for inclusion archived due to age This issue has been archived; please open a new issue for any further discussion documentation Relates to ESLint's documentation enhancement This change enhances an existing feature of ESLint
Projects
No open projects
Development

No branches or pull requests

4 participants