Coverage decreased (-0.31%) when pulling 3f7111ce1920493fd55835e64049a34a852a711d on cm/support_multiple_levels_of_nesting into 764127f0d957b6c0d4ffe476bbc2fa5bca6b5dfd on master.
Coverage increased (+0.01%) when pulling 3f7111ce1920493fd55835e64049a34a852a711d on cm/support_multiple_levels_of_nesting into 764127f0d957b6c0d4ffe476bbc2fa5bca6b5dfd on master.
Coverage increased (+0.01%) when pulling a1fd748e90f5bda2d2e492cf71d344806daf9326 on cm/support_multiple_levels_of_nesting into 764127f0d957b6c0d4ffe476bbc2fa5bca6b5dfd on master.
Coverage increased (+0.01%) when pulling b2b83684cec27bba6d800d4f81025cd236c930e6 on cm/support_multiple_levels_of_nesting into 764127f0d957b6c0d4ffe476bbc2fa5bca6b5dfd on master.
At the moment this type of fixture is not supported:
The
!rel user1.id
ends up turning intouser1.id
because we only look at the first two levels.This diff seeks to support parsing relationships for multiple levels of nesting.