andymoreland / tsunami Goto Github PK

I have a package that exposes "namespaces" as one-level nested folders:

import { sym } from "mypackage";
import { AOptions } from "mypackage/modulea";
import { BOptions } from "mypackage/moduleb";

The second two imports above are not accessible from the root package, so Tsunami is unable to provide those import suggestions. In practice, they're implemented as root-level modulea.d.ts and moduleb.d.ts files.

In general, importing from not-package-root seems unideal. Perhaps this can go in a .tsunami file with hints for downstream projects, or a custom package.json key that Tsunami looks for?

Right now I get thrown off by auto-imports when typing in code comments. I'm using tsunami-code v0.7.0.

Request: don't auto-import when typing in comments.

Thanks for your plugin, with latest changes it works great on windows. I have few more issues now:

1. Popup appears inside // comments
2. Popup appears inside string literals "" or ''
3. Popup appears inside destructuring expressions
4. Property access expression. To reproduce this case hide TS completion popup (by moving cursor or pressing esc) then try to type again to complete statement. The popup will mix object properties with import completions.
5. It should not suggest import completion if there is local variable with same name as exported element.
   May be there are few more contexts which are not making sense for completion import.

Also please make an option to disable import completion popup if these issues are hard to resolve (in this case it's better to wait for native TS auto-import implementation) .

VScode 1.8.1
Tsunami-vscode 0.5.2
Windows 10

In my project, I have folders which have an index.ts which re-export all "public" symbols from that folder. I want my imports to come from that folder when applicable:

// module/index.ts
export interface Foo {
  bar: string;
}

// other/file.ts
// current import emit:
import { Foo } from "../module/index";
// expected import emit:
import { Foo } from "../module";

"foo.ts" next to "foo" causes issues with relative imports

User has internal module structure that re-exports symbols. Prefers that the symbols are exported from index files rather than from the source modules.

If I have something like: FooBar and put my cursor in between the B and the a to import FooBar, it will not remove the suffix properly and give me FooBarar

goal is to support importing, for example, lodash methods underneath a consistent namespace import.

tsunami-code 0.5.1
VScode 1.8.1
Windows 10

I have few problems which makes this plugin totally unusable on Windows:

1. When importing symbol it rewrites all existing relative paths from ../../path/to/file to ..\..\path\to\file
2. Importing some symbol from project is resulting to absolute path name instead of relative one