rvion

This issue is preventing us from adopting the tool

I also see this error with plain `pg` lib (without using TypeORM or any other orm). as @charmander said, an 'error' event is emmited. ``` pool.on('error',...) ``` but it is...

I would really like to have qualified module re-export --------- I would also like being able to know easilly where does a module comes from. ```purescript import MyPrelude -- TarPath...

> That underscore-qualified naming scheme looks horrendous to me personally 😄 I'd just use the actual qualification I imagine. that was one of the many problems 😄 I tried many...

we should also add `.keepTextChuck()` (similar to `.keepExif()`, `.keepMetadata()`), so conversion to compatible format preserve those, possibly mapping them to similarly named exif metadata if target format has no tEXt...

big +1 on the request. Previous discussions seemd to imply that pre-existing line breaks should have been preserved. That appears not to be the case. IMO: it's now as annoying...

@thorn0 > There are a few exceptions to this (object literals, method decorators, and some cases in JSX), but those are cases where a better trade-off couldn't be found at...

Hi @thorn0 , thanks for your answers ! > @rvion I strongly believe preserving manual formatting dilutes the value of Prettier. I have no strong opinion on this but tends...

For now, I'll just type [`START`,`/`,`/`,`enter`,`.`,`METHOD_CHAIN`] and will just loose 3 keystrokes in the process. The drawbacks are : - It's a bit annoying for existing codebases - It's harder...

> How can we distinguish between a valuable intentional line break and a random line break that doesn't convey any important information and was inserted we can't, and that's exactly...