atom-react-autocomplete icon indicating copy to clipboard operation
atom-react-autocomplete copied to clipboard

Suggestion/Feedback: Minor Changes to Help with Install

Open MutableLoss opened this issue 9 years ago • 0 comments

I've been through so many auto-completion plugins in the past year for React/JSX, and when I see a new one like this, which offers what it does, and helps replace the React plugin (which offers a bunch of functionality in one package, causes conflicts with many others, and doesn't always work), I'm always for trying to help out by spreading the word, and giving feedback. If you are all open to feedback, I thought of a few minor suggestions to help you with your install, and at least get users using your plugin right away, and bask in the awesomeness (from what I've seen).

1. First off, I love that you are adding auto-complete for everything in the project, but does it have to happen when starting out? Could new users have a default completions.json to work with, and have the option to add imports, and other project specific options later?

1a. If you were to create a default completions.json, this could even be something that lived with the Atom package, and project-based completions (node_modules, src), could be added to the project directory's completions file (similar to atom-ternjs).

3. When generating the completions, why can't the cli be installed with the atom package, and referenced there? You almost always know where an atom config dir is going to be, and if someone uses a custom directory, give them a package variable as an option in the package settings so that they can point the package to that location.

4. Lastly, why not have a generate command within Atom? I'm sure this is probably something planned for the future as well, but even using some automation through a install of the pty.js library, or something like that allowing you to automate and still use a shell.

I hope you do not take these as insults, or attacks of any kind at all, as they were certainly not written to be portrayed as such. I would really like to see this project become more user-friendly, and reach the masses. I simply wanted to leave these suggestions, because I know that an outside view can sometimes be very helpful when focusing on a certain model for so long. Who knows, these might already be ideas on the back-burner, but I at least wanted to give you some feedback from the other side of the fence. :)

MutableLoss avatar Sep 15 '16 21:09 MutableLoss