Fix resolving key path for matte layers

[alex-dorokhov]

This PR adds the check for matte layer name before going deeper during key path resolution.

Without the fix the key path matches children inside the matte layer even though it should not, for example:

'layer_1.group_1.child_1' could match 'layer_1.matte_1.group_1.child_1'

With the fix it is not possible anymore.

[gpeal]

Could you add a snapshot test for this? You can follow other test cases here as an example.

It may be difficult to fully run the tests locally because it requires API keys but you can comment out other test cases and then put a breakpoint here to view the bitmap snapshot.

[github-actions]

Snapshot Tests
API 23: Report Diff
API 31: Report Diff

[gpeal]

Could you add a snapshot test for this? You can follow other test cases here as an example.

It may be difficult to fully run the tests locally because it requires API keys but you can comment out other test cases and then put a breakpoint here to view the bitmap snapshot.

Alternatively, if you push a test, it'll run on CI and post a comment back. It just won't run until I click approve so the turnaround time will be longer.

[gpeal]

@alex-dorokhov would you like to update this so we can get this PR landed?

[alex-dorokhov]

@alex-dorokhov would you like to update this so we can get this PR landed?

Sorry, that it got so long for me to reply.

There is already a test for dynamic properties of matte layers. I believe it had wrong results before the fix and now it is good, so should be accepted. Please, look at the second report here #2544 (comment)

I've debugged the test to be sure.

Before the fix

This line has been called twice when callback is added (so two matte layers have been matched).

Please, notice that "Shape Layer 3" should not be matched:

After the fix

This line has been called only with "Shape Layer 1":

I've also attached before and after videos for convenience:

before.mov

after.mov

[gpeal]

@alex-dorokhov Thanks for clarifying!