jugglinmike / proposal-conflict-comment Goto Github PK

In your example:

function onRequest() {
<<<<<<< HEAD
  var screen = document.querySelector('.screen7');
=======
  var screen = document.getElementsByClassName('screen8')[0];
>>>>>>> refactor-overlay

By treating the conflict markers as comments, screen will silently be set to screen 8, instead of 7 - this could cause a much harder to triage production bug if the wrong screen got updated - perhaps because the logic below (that uses screen) did not conflict, and assumes screen 7.

It should have runtime semantics that read the mind of the developer to decide which git conflict branch should be used instead of silently ignore them all.
I'd like to see that kind of supernatural feature to be implemented in the engines 🎉

the proposal inside README.md is prefixed with a message saying that it's a "joke". surely the repo has been compromised by an outside party.

Seems completely overkill to me. You're asking to modify a language used by millions of people just to support mistakes done by a really really few people which doesn't know how to properly use a tool...

In a real dev environment (company business) this never ever append => tests, ci checking/building code, lint, version control, etc... Moreover, github warns you about this, and of course you create branches and doesn't push on master... So typically, your example should absolutely never append, except for extreme amateurs