Potential statement mapping (Move And Rename Method)

[pedramnoori]

Problem

Two statements reported as non-mapped has the potential to match

Commit

Here

Refactoring

Move And Rename Method private getFlags(edgePointer long, reverse boolean) : long from class com.graphhopper.storage.GraphHopperStorage to package getFlags_(tmpPropAccess InternalGraphPropertyAccess, edgePointer long, reverse boolean) : long from class com.graphhopper.storage.BaseGraph

Description

There is a pair of statements reported as non-mapped leaves: 1- return reverseFlags(edgePointer,res); Line 710, parent version 2- resFlags=tmpPropAccess.reverseFlags(edgePointer,resFlags); Line 686, child version

Based on the manual validation of the refactoring, these two statements can match together. The changes are justifiable by a Rename Variable refactoring, and the mechanics of the Move Method refactoring.