Skip to content

Conversation

@elwynelwyn
Copy link
Contributor

The generated paths always had a hardcoded ./ prefix. This resulted in
paths like this:
import IWow from './../foo/bar/IWow';
While technically correct, the initial ./ is redundant, and looks a
bit silly.
I've removed the hardcoded ./ and added a check for the first
character of the relative path being a .. This means it will not be
added, unless the import is for a file in the same directory as the
source file, in which case it will result in ./IWow

The generated paths always had a hardcoded `./` prefix. This resulted in
paths like this:
`import IWow from './../foo/bar/IWow';`
While technically correct, the initial `./` is redundant, and looks a
bit silly.
I've removed the hardcoded `./` and added a check for the first
character of the relative path being a `.`. This means it will not be
added, unless the import is for a file in the same directory as the
source file, in which case it will result in `./IWow`
@GabiGrin
Copy link
Owner

GabiGrin commented Feb 3, 2016

Hey, sorry for the long delay.
Can you try and fix the conflicts? Probably caused by your other PR that was merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants