Autocomplete is not working
Closed this issue · 4 comments
Prerequisites
- Put an X between the brackets on this line if you have done all of the following:
- Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
- Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
- Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
- Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
- Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages
Description
[Description of the issue]
Steps to Reproduce
- [First Step]
- [Second Step]
- [and so on...]
Expected behavior: [What you expect to happen]
Actual behavior: [What actually happens]
Reproduces how often: [What percentage of the time does it reproduce?]
Versions
You can get this information from copy and pasting the output of atom --version and apm --version from the command line. Also, please include the OS and what version of the OS you're running.
Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.
Thanks for reaching out!
We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us half way 😀
@50Wliu I just saw this issue, and honestly, I simply downloaded atom to see if I can quickly prototype an idea, and selected Generate Atom Package, then as soon as I opened the view JS the first thing that threw me off is that there was no auto complete atom.workspace.a assuming I was going to see alternatives to the atom.workspace.addModalPanel... I realize you have a process, but I hope this can show the urgency and the possible loss of interest that people may be feeling if they are just looking around (not avid atom users as I am sure those are too many to count).
Please just look into defacto auto-complete, fresh download (about/version: 1.25.0) on macOS where atom.… in new Generate Atom Package is not working.
Thanks 👍
@SMotaal If you could open a new issue and describe your exact reproduction steps, I would be happy to take a look!
@50Wliu I appreciate your process, in fact I subscribe to it when collaborating on projects, but it seems to me that the lines are getting a little blurred (regardless of how messy the report) because ultimately customers reporting issues is not a favour to them but rather their (maybe not very clear) effort to try to help you in your quest to deliver a good product to all the other customers (because for them it has already not been the best experience and they want to not let this be the case for the rest of us).
So no, it is not okay to leave your flagship product broken, because you have a process, honestly.
Please don't expect customers to be part of your organizational culture, or at least, maybe give them the benefit of the doubt, they might not have the technical benefits that are acquired by being in your place.