Major refactor of the way personalDataDefinitions are parsed for the cardholder, refs:
1
Initially I was going down a path of implementing a cache of the personalDataFields which is unnecessary as the cardholder detail response will always return what we need. Hence it makes sense to parse the personalDataDefinitions (see commit) and then make the top level keys accessible as aliases.
Major refactor of the way
personalDataDefinitionsare parsed for the cardholder, refs:1
Initially I was going down a path of implementing a cache of the personalDataFields which is unnecessary as the cardholder detail response will always return what we need. Hence it makes sense to parse the personalDataDefinitions (see commit) and then make the top level keys accessible as aliases.