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
Sure. Because Git's built in diff/merge/rebase strategies work on a line-by-line basis, not function-by-function or expression-by-expression, the merge conflict markers that it generates are at the start and end of the smallest number of lines that can be grouped together to a show a change, rather than at the end of each affected function or expression. This can make resolving merge conflicts very difficult, especially when there are many levels of nesting in the syntax.
Hmm, I can see how this would be useful for projects that use Prettier, but accept contributions which may not already be formatted with Prettier. Not sure how feasible it would be to support non-Prettier projects though.
Even if the merge driver isn't implemented, the same effect could be achieved by running Prettier on both branches before merging them, right?
Have you considered extending this project so it can be used as a git merge driver?
The text was updated successfully, but these errors were encountered: