Long-length import statements could wrap

In the example:

import someCoolUtilWithARatherLongName from '../../../../utils/someCoolUtilWithARatherLongName';

Which is 94 characters. Given that I want to wrap at 80 characters, my subjective ideal would be

import someCoolUtilWithARatherLongName
  from '../../../../utils/someCoolUtilWithARatherLongName';

This isn’t an issue with the import { name } from 'source' syntax.

[jlongster]

I would say we just let it go past the max length threshold. It’s not common for the above to happen, so I don’t think we should worry about it too much.

[merlosy]

@PavelPikat I found a better option than ignoring tslint. You can add exception for specific regex. Prettier will have the lead for managing imports and exports, since it has a special way to deal with them.

// edit tslint.json
"max-line-length": [
     true, 
    { 
        "limit": 140, 
        "ignore-pattern": "^import |^export {(.*?)}" 
    }
],