Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parse and handle git merge conflicts well #59

Open
nickavv opened this issue Aug 1, 2017 · 0 comments
Open

Parse and handle git merge conflicts well #59

nickavv opened this issue Aug 1, 2017 · 0 comments

Comments

@nickavv
Copy link
Member

nickavv commented Aug 1, 2017

When using git, developers may run into merge conflicts. These are represented directly in code as such:

<<<<<<< HEAD
            // code from your branch
=======
            // code from merging-branch
>>>>>>> commit hash or description

In Eclipse the Java parser completely chokes on these extra lines and you get a sea of compile errors. My recommendation is that in Corona we parse the three merge conflict lines and make it visually obvious what is happening. To avoid errors related to part of the conflict referencing classes that don't exist or whatnot I recommend we not even bother trying to compile the code inside the merge chunks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants