-
Notifications
You must be signed in to change notification settings - Fork 22
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
Different ac behaviour on js and ts files #160
Comments
@LionyxML We actually used Would it be acceptable to put a https://github.com/ananthakumaran/tide#javascript If so, we could see if that file exists, and then load tide in stead of a vanilla JS environment.
|
Oh, and no need to apologize ever. Really appreciate ways that this can be improved. |
Hello there! I asked around about having a fallback for when jsconfig.json or tsconfig.json is not present into the directory, but I guess I am too dumb to understand the reason (lol). In short. For projects I maintain, it is ok to do so. For projects I do not have any decision power, I will probably have to manage it locally. I would love this feature, but I do not think it is for everyone (due to jsconfig mandatory presence), it might be some option to set in frontside custom-group. Points to VSCode in this regard. If no config is present, it runs typescript in the background using its own defaults. |
There are a couple of reasons.
Maybe we can have defaults for these? Not sure how that could work... |
Hello again! Sorry to spam you guys like this. :D
As I am more then happy editing a new .tsx / .ts project, but I happened to be maintaining some older JS code also.
And now emacs behaves differently. No auto complete and no docs over functions. I know VsCode made me spoiled by providing the same linting for both .js and .ts files, am I asking to much expecting it to behave the same?
Inside a .tsx file if I type
console.
I get the following suggestions:The same if the file is a .ts:
But inside a .js (also jsx) file:
My modes:
Inside JS(X) files:
Inside TS(X) files:
For comparison, on both js(x) and ts(x) inside VSCode:
The text was updated successfully, but these errors were encountered: