Fix user_data.address extraction to handle array format#17
Open
ZLeventer wants to merge 1 commit intolinkedin-developers:mainfrom
Open
Fix user_data.address extraction to handle array format#17ZLeventer wants to merge 1 commit intolinkedin-developers:mainfrom
ZLeventer wants to merge 1 commit intolinkedin-developers:mainfrom
Conversation
…elopers#10) user_data.address can be either an object or an array (e.g., address[0]). Extract the first element when address is an array, fall back to the object as-is otherwise.
This was referenced Apr 24, 2026
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
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.
Summary
Fixes #10.
user_data.addresscan be either a plain object or an array (e.g.,address[0]). The current code assumes it is always an object, which causes incorrect field extraction when an array is provided.This change checks the type of
user_data.addressat initialization and extractsaddress[0]when it is an array, falling back to the object as-is otherwise. All downstream consumers (getUserFirstName,getUserLastName,getUserCountryCode) work unchanged.Changes
template.tpl: Replaceconst user_address = user_data.address || {};with a two-step assignment that usesgetType()(already imported) to detect arrays and unwrap the first element.