Revert change to BillingBlock to support hidden fields. #12391
Merged
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
Partial revert of #12332 per feedback from @mattwire
Before
Some processors would have experienced a regression from #12332
After
Line causing regression removed, field addition handled differently
Technical Details
Per discussion with Matt Wire this is actually unnecessary, if we define 'id' in the payment fields
metadata. This is a bit too much like spooky magic but it ... erm .. works
Comments
We could probably handle adding 'id' in the Payment helper classes. OTOH for most processors just one hidden token field is needed so most processor devs may not hit the need to know to add the id attribute
@mattwire please confirm this is 'good to merge'