Bug 293031 - Improvement suggestion: apply same formatting rules to both sides before comparing
Summary: Improvement suggestion: apply same formatting rules to both sides before comp...
Status: CLOSED DUPLICATE of bug 127237
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Compare (show other bugs)
Version: 4.0   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Compare-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 293033 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-10-22 09:04 EDT by Cassio CLA
Modified: 2009-10-22 09:43 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cassio CLA 2009-10-22 09:04:03 EDT
User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; InfoPath.2; MS-RTC LM 8)
Build Identifier: 20090621-0832

My suggestion is to have an option to format code before comparisons. I do maintenance in legacy systems, and all code that needs to be changed is formatted before saving to as an attempt to standardize that old code. When we will proceed with the merges, the files are so different because of the formatting that we can't see exactly what was changed. This way, being able to format the code before comparing would point us only what was in fact changed. Of course this formatting won't be saved on files; it will be used only to make comparison easier. Also, this can be a option of format configuration, allowing people to toggle this feature on/off. Thanks for your time.

Reproducible: Always

Steps to Reproduce:
1. Pick up an unformatted code
2. Change something in it and format before saving
3. Compare with a previous version
Comment 1 Cassio CLA 2009-10-22 09:16:45 EDT
*** Bug 293033 has been marked as a duplicate of this bug. ***
Comment 2 Tomasz Zarna CLA 2009-10-22 09:43:36 EDT

*** This bug has been marked as a duplicate of bug 127237 ***