Query: Complex case of null check removal

[smitpatel]

        [ConditionalTheory]
        [MemberData(nameof(IsAsyncData))]
        public virtual Task Null_check_removal_applied_recursively(bool isAsync)
        {
            return AssertQuery<Level1>(
                isAsync,
                l1s => l1s.Where(l1 =>
                    (((l1.OneToOne_Optional_FK1 == null
                        ? null
                        : l1.OneToOne_Optional_FK1.OneToOne_Optional_FK2) == null
                            ? null
                            : l1.OneToOne_Optional_FK1.OneToOne_Optional_FK2.OneToOne_Optional_FK3) == null
                                ? null
                                : l1.OneToOne_Optional_FK1.OneToOne_Optional_FK2.OneToOne_Optional_FK3.Name) == "L4 01"));

Since each test is wrapped in bracket we currently fail to remove null check.
Translation fails because entity equality will put Id access on conditional expression which is not entity shaper.

[smitpatel]

Such query constructs are also generated from AutoMapper (in some cases? Never seen all users with this kind of pattern). Removing milestone to reconsider priority.

[smitpatel]

I have an idea for this. Poaching.

[Erythnul]

Hi! Any way I can help move this along? Would love to get back to using AutoMapper's ProjectTo instead of our current workaround.