Bug: Fixing null/undefined theme argument for the WordPressBlocksProvider

[colinmurphy]

Tasks

• I have signed a Contributor License Agreement (CLA) with WP Engine.
• If a code change, I have written testing instructions that the whole team & outside contributors can understand.
• I have written and included a comprehensive changeset to properly document the changes I've made.

Description

Fixing an issue with the WordPressBlocksProvider that doesn't allow the theme argument to be null.

Related Issue(s):

#1986

Testing

I have tested this on 2 different ways

1. Using this current repo and the next/example block support
2. Setting up Faust using this branch
3. Coping changes into a current Faust setup

Screenshots

Documentation Changes

Dependant PRs

[changeset-bot]

⚠️ No Changeset found

Latest commit: d7146e3

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

[github-actions]

📦 Next.js Bundle Analysis for @faustwp/getting-started-example

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

[colinmurphy]

@moonmeister Can you review this please and see if you can still replicate issue #1986 please

[colinmurphy]

@moonmeister I need to update this PR as some of the logic isn't correct

[colinmurphy]

@moonmeister This is ready for review.

[moonmeister]

Can you explain why/how this fixes the issue?