[subs] add useACOM boolean field to determine whether to use advancedCommerceData or requestData as the custom option key when purchasing#3
Merged
charleschen merged 1 commit into12.16.3-discordfrom Nov 19, 2025
Conversation
tjmabey
approved these changes
Nov 14, 2025
charleschen
force-pushed
the
subs/acom-update-purchase
branch
2 times, most recently
from
bbdbe45 to
fb2e188
Compare
…dCommerceData` or `requestData` as the custom option key when purchasing
charleschen
force-pushed
the
subs/acom-update-purchase
branch
from
fb2e188 to
5d752e3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Priority P1
What
Why
Tests
Task