fix: support ChainExpression in await-interactions rule

[VinceMalone]

Issue: #86

What Changed

in existing use-cases of the await-interactions rule, the code is assumed to be valid when the CallExpression node is the immediate child of an AwaitExpression node.

await FirstStory.play(context); → AwaitExpression > CallExpression > …

await FirstStory.play!(context); → AwaitExpression > CallExpression > TSNonNullExpression > …

to support an expression with an optional chain, the logic to determine if the expression was properly awaited now checks if the parent of the parent of the CallExpression node is an AwaitExpression.

await FirstStory.play?.(context); → AwaitExpression > ChainExpression > CallExpression > …

Checklist

Check the ones applicable to your change:

• Ran yarn update-all
• Tests are updated
• Documentation is updated

Change Type

Indicate the type of change your pull request is:

• maintenance
• documentation
• patch
• minor
• major

[yannbf]

Thank you so much for your contribution @VinceMalone !! I added a small fix and this is good to go.
Before merging though, would you like to edit your author email from your commit? Seems as if it's not set and I think this might end up not adding you as a contributor to this project as a result.

Thank you!

[VinceMalone]

thanks @yannbf. I think I fixed the email; lemme know if it's still not working.

[yannbf]

thanks @yannbf. I think I fixed the email; lemme know if it's still not working.

It's perfect now! Thanks once again, for using this library and for making it better!

[github-actions]

🚀 PR was released in v0.5.9 🚀