You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My experience is specifically with typescriptreact, where vim-prettier changes the default typescriptreact to typescript. This breaks my completion plugin, for example, which depends on typescriptreact for jsx apparently.
The question is why should vim-prettier touch those filetype detections at all? I feel like if they get correctly set by default vim or nvim, vim-prettier shouldn't interfere. Maybe it's from a time when those were not set correctly?
The text was updated successfully, but these errors were encountered:
Just for my curiosity: why does vim-prettier have to declare filetypes at all? Why not leave that to vim runtime or to specialised plugins? Is it a best practice because it has ftdetects?
This is just a guess but I believe they felt that certain filetypes might not interface well with prettier, or probably an early bug fix. I myself would rather stick to vim runtime.
My experience is specifically with typescriptreact, where vim-prettier changes the default typescriptreact to typescript. This breaks my completion plugin, for example, which depends on typescriptreact for jsx apparently.
The question is why should vim-prettier touch those filetype detections at all? I feel like if they get correctly set by default vim or nvim, vim-prettier shouldn't interfere. Maybe it's from a time when those were not set correctly?
The text was updated successfully, but these errors were encountered: