Skip to content

Editor configs #35

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

Closed
amilajack opened this issue Oct 29, 2016 · 6 comments
Closed

Editor configs #35

amilajack opened this issue Oct 29, 2016 · 6 comments

Comments

@amilajack
Copy link

I think it would be great if we could include an editor configuration describing how to setup IDE/text editors for these tools. Proper integration significantly improves developer experience.

@cpayne22
Copy link

+1
I'm coming from a Asp.Net / Visual Studio background. I don't need to use Visual Studio, and if I went for a contracting gig, I'm sure others wouldn't be using Visual Studio.

But it's not clear to me what they would be using.

It doesn't have to be war & peace, but if you're catering to a novice, it's a pretty big assumption to make that they can't install Node, but the IDE is all sorted...

@amilajack
Copy link
Author

@verekia

And the only way to stay generic and please everyone is via the console.

IMO, if we do that, it doesn't offer that great of a development experience when compared to running flow while typing. Just by at the amount of downloads eslint-linter gets (449,793), you can tell that there's quite a demand for linting on the fly instead of using the CLI.

it does not add much value compared to setting up ESLint and Flow in your IDE

I agree. I designed the plugin for large scale projects that are already using eslint and want to add flow integration easily. Flow integration doesn't have that much support across editors when compared to eslint. So its a tradeoff of having users of certain editors not have a plugin for their editor and not having full integration (autocompletion). Should we recommend both, with the eslint flow plugin as an alternative if no editor support exists for their editor?

@verekia
Copy link
Owner

verekia commented Nov 1, 2016

I absolutely agree with linting as you type being essential.

Ohh that makes a lot of sense, you have a good point.

Okay so here is the plan:

  • I'm going to write a chapter about Atom, which has a good flow support. The plugin shouldn't be needed there.
  • I'll let the community write chapters about other editors, and will recommend your plugin for these other editors if the flow support is not as good as ESLint support.

Sounds good?

@amilajack
Copy link
Author

@verekia yup! Agreed

@verekia
Copy link
Owner

verekia commented Nov 3, 2016

Actually, let's keep that one open until the Atom chapter is out!

@verekia verekia reopened this Nov 3, 2016
@verekia verekia changed the title PR: Add editor config section Editor config chapters Mar 5, 2017
@verekia verekia changed the title Editor config chapters Editor configs Mar 5, 2017
@verekia
Copy link
Owner

verekia commented Mar 5, 2017

Created a more specific issue: #148

@verekia verekia closed this as completed Mar 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants