I've recently noticed that when having two merged cells next to one another, the ExcelRange that matches both cells is seen as merged.
For instance, using this code:
```
var file = new FileInfo("yourFile.xlsx");
using (var ep = new ExcelPackage(file))
{
var ws = ep.Workbook.Worksheets[1];
ws.Cells[25, 8, 25, 13].Merge = true;
ws.Cells[25, 14, 25, 16].Merge = true;
var isResultingRangeMerged = ws.Cells[25, 8, 25, 16].Merge;
ep.Save();
}
```
... you will notice that isResultingRangeMerged returns true.
After taking a look at ExcelRangeBase.cs, it seems that when a range contains only merged cells, the whole range is considered merged, even when it actually contains several distinct cells.
Hence my question: is this an expected behaviour?
For instance, using this code:
```
var file = new FileInfo("yourFile.xlsx");
using (var ep = new ExcelPackage(file))
{
var ws = ep.Workbook.Worksheets[1];
ws.Cells[25, 8, 25, 13].Merge = true;
ws.Cells[25, 14, 25, 16].Merge = true;
var isResultingRangeMerged = ws.Cells[25, 8, 25, 16].Merge;
ep.Save();
}
```
... you will notice that isResultingRangeMerged returns true.
After taking a look at ExcelRangeBase.cs, it seems that when a range contains only merged cells, the whole range is considered merged, even when it actually contains several distinct cells.
Hence my question: is this an expected behaviour?