Test glob with parent directory

[sjarva]

Which issue, if any, is this issue related to?

Closes #3273

Is there anything in the PR that needs further explanation?

I think that these added unit tests should have been in __tests__/standalone-globs.test.js, but as the needed test case has to have the styles in a parent directory, and all unit tests have to be in __tests__, I created a new folder standalone-glob-parent-test that contains all the needed files.

I also created a unit test that has a parent directory (../) and a wildcard (**/) in the glob, since although this is not very common, it's a possible case. And as the documentation says that [the unit tests] should be comprehensive and systematic, I thought this is a valid test case to have.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 21cfd87

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ybiquitous]

@sjarva Thanks for opening the pull request. The added tests look good to me. 👍🏼

By the way, a linting job in CI fails. Could you fix it, please?

[sjarva]

@sjarva Thanks for opening the pull request. The added tests look good to me. 👍🏼

By the way, a linting job in CI fails. Could you fix it, please?

Absolutely! I'm not totally sure did I fix it correctly, because the first time that I ran npm run format (to fix the prettier errors that the CI/CD pipeline), there was no changes that I could commit 🤔

I added the new test folder to .prettierignore, as has been done with other style files that are in /fixtures.

[ybiquitous]

Thank you. LGTM 👍🏼

[jeddy3]

Thank you!