Prevent rendering fields if should not; use hosted pages instead #118
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR introduces logics to avoid rendering hosted fields under circumstances that it shouldn't be rendered.
Background
With 3.1.0, we introduced these 2 changes:
As a result an unexpected behaviour was introduced, with which it attempts to render hosted fields unconditionally, even though inline fields are disabled or the publishable key is unset.
It's also worth to mention that there's a non-intuitive design in the WC side for checkout shortcodes. Blocks just need an extra logic to control the behaviour.
Changes introduced
This PR makes these two specific changes: