capaj vscode-exports-autocomplete issues

capaj / vscode-exports-autocomplete

finds javascript ES6 exports in your project and autocompletes them when writing javascript statements

MIT License

18 stars 6 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Extension causes high cpu load

#45 theosyslack opened 5 years ago
0
Import order intelliSense

#44 pvpshoot opened 6 years ago
0
Module resolve

#43 pvpshoot opened 6 years ago
0
flow import type is not properly handled

#42 capaj opened 6 years ago
0
Cannot match against 'undefined' or 'null'.:

#41 cjhoward92 closed 6 years ago
1
object property token was imported

#40 capaj opened 6 years ago
0
when writing a new variable, it should not autocomplete

#39 capaj opened 6 years ago
0
when pasting inside a string we should not insert imports

#38 capaj opened 7 years ago
0
try to recognize when writing a key name and don't offer any items for autocomplete

#37 capaj closed 7 years ago
0
Feature Request: Add option to exclude directories in user settings

#36 aga5tya opened 7 years ago
2
TypeError: Cannot match against 'undefined' or 'null'.

#35 kurtextrem closed 7 years ago
1
don't autocomplete when writing a jsx element property

#34 capaj closed 7 years ago
0
Feature Request: Understanding "import type" from flow

#33 axelnormand opened 7 years ago
2
when pasting inside a string literall, we should not autocomplete

#32 capaj closed 7 years ago
1
for autocomplete provider filter out items by export path

#31 capaj opened 7 years ago
0
when preceding character is a . we should not autocomplete

#30 capaj closed 7 years ago
0
when pasting and looking for words to import, utilize esprima-undeclared-identifiers

#29 capaj closed 7 years ago
0
when pasting a code from clipboard, add imports as well

#28 capaj closed 7 years ago
0
when rewriting an existing jsx token <> into another parsing of the file fails

#27 capaj opened 7 years ago
0
console.warning is not a function, rename to console.warn

#26 cheapsteak closed 7 years ago
0
add command to refresh the cache of imports

#25 capaj closed 7 years ago
0
introduce "add missing imports" command

#24 capaj closed 7 years ago
1
add a command to add any missing imports

#23 capaj opened 7 years ago
0
add project specific moduleResolverRoot option

#22 capaj opened 7 years ago
1
add a feature to install an npm module directly from the editor

#21 capaj opened 7 years ago
0
support completing decorators

#20 capaj closed 7 years ago
1
Imports default to using backslash rather than forward slash on Windows.

#19 dealvz closed 7 years ago
5
if package.json has "engines" then we should also offer node.js built-in modules

#18 capaj opened 7 years ago
0
Separate style-info module

#17 flying-sheep opened 7 years ago
2
Feature request: Support quote styles

#16 doctyper opened 7 years ago
8
Feature request: Support file extensions

#15 doctyper opened 7 years ago
0
packages that export multiple things are not autocompleted when one thing is already imported

#14 capaj opened 7 years ago
0
add spacing in import specifiers setting

#13 capaj opened 7 years ago
0
when exports loaded from cache, parse changed files in git

#12 capaj closed 7 years ago
1
when package.json changes, rescan node_modules

#11 capaj opened 7 years ago
0
generating extra import statements

#10 capaj closed 7 years ago
0
when inside a string token, don't provide any completions

#9 capaj closed 7 years ago
0
add completion of tokens from existing import statements

#8 capaj opened 7 years ago
0
default export name should be capitalized when JSX is present

#7 capaj closed 7 years ago
1
parse semicolon rule from eslint

#6 flying-sheep closed 7 years ago
3
add details to CompletionItems

#5 capaj closed 7 years ago
0
add configs

#4 capaj closed 7 years ago
0
when writing import * we should just replace the current line

#3 capaj closed 7 years ago
1
cache the exports

#2 capaj closed 7 years ago
0
destructuring in generated imports

#1 capaj closed 7 years ago
0