| Reporter |
Tim Herby (Tim.Herby)
|
|---|---|
| Created | Feb 10, 2012 2:14:06 AM |
| Updated | Feb 10, 2012 2:15:25 AM |
| Priority | Normal |
| Type | Feature |
| Fix versions | No Fix versions |
| State | Submitted |
| Assignee | Unassigned |
| Subsystem | Options |
| Affected versions | 6.1 |
| Fixed in build | No Fixed in build |
This solution would make team-sharing of settings much more predictable.
Scenario:
Expected:
Actual:
Solution:
Notes:
I have already checked that when settings are saved to .DotSettings files, they are honored even if they are the default value. Example:
So it is possible to do this manually if you create the rows in the .DotSettings file. The proposed change is only to the Export and Save mechanisms.
Scenario:
- Sharing team settings
- Export your local settings to a file
- Everyone mounts it (or references it in a Solution layer)
- One developer has overridden a setting which you hadn't overridden
Expected:
- Everyone has all the settings exactly as exported
Actual:
- Even with the team settings, they get their override
Solution:
- Add an option to the export function to export all values, not just the incremental differences from the default Resharper values.
- There would need to be a flag in the file, so that when further values are saved to it using the "Save" and "Save To " default values are not ignored and wiped out.
Notes:
I have already checked that when settings are saved to .DotSettings files, they are honored even if they are the default value. Example:
<s:String x:Key="/Default/CodeInspection/Highlighting/InspectionSeverities/=InconsistentNaming/@EntryIndexedValue">WARNING</s:String>
So it is possible to do this manually if you create the rows in the .DotSettings file. The proposed change is only to the Export and Save mechanisms.