toHaveProperty doesn't support array syntax

[kalvenschraut]

Describe the bug

Not sure if this is really a bug or not, but since docs talk about jest and vitest compability this is one area I ran into that seems to be the exception. Basically jest allows you to specify the keys in an array instead as talked about here. The edge case I ran into is mainly the fact that a key has a dot in it (key is a domain name) so when we pass the domain name to the toHaveProperty function it tries to get the property deeply that doesn't exist. Solution Jest has is to wrap it in an array but then we get, the argument to property must be string when using nested syntax which seems to be from chai itself.

Reproduction

test('to Have Property can receive an error', () => {
  const domainKey = 'somedomain.com'
  const object = {
    [domainKey]: 'foo'
  }
  expect(object).toHaveProperty([domainKey], 'foo')
});

System Info

OS: Linux 5.10 Gentoo/Linux
                                                                                                                                                                                       
 CPU: (4) x64 Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
                                                                                                                                                                                    
 Memory: 4.72 GB / 31.33 GB
                                                                                                                                                                                     
 Container: Yes
                                                                                                                                                                                     
 Shell: 5.1.8 - /bin/bash
                                                                                                                                                                                     Binaries:
                                                                                                                                                                                    
  Node: 16.10.0 - /usr/bin/node
                                                                                                                                                                                    
  npm: 6.14.15 - /usr/bin/npm
                                                                                                                                                                                     
  Watchman: 4.9.0 - /usr/bin/watchman
                                                                                                                                                                                    Browsers:
                                                                                                                                                                                     
  Chromium: 95.0.4638.69
                                                                                                                                                                                    
   Firefox: 91.3.0esr

Used Package Manager

pnpm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.