Skip to content

Fixed issue #7: JSON parsers uses always default configuration - #16

Open
marwoj wants to merge 1 commit into
arunisrael:masterfrom
marwoj:fix_#7/parseJsonAsConfigured
Open

Fixed issue #7: JSON parsers uses always default configuration#16
marwoj wants to merge 1 commit into
arunisrael:masterfrom
marwoj:fix_#7/parseJsonAsConfigured

Conversation

@marwoj

@marwoj marwoj commented Oct 6, 2015

Copy link
Copy Markdown

Fixed issue #7: parseNSJSON method don't read keys from options always use defaults.

Now 'req' object which extends 'defautls' about user configuration is passed to parseNSJSON and parsePDJSON functions, so valid fields 'nearbySearchKeys' and 'placeDetailsKeys' are used to parse JSON and return what user requested"

…ions always use defaults.

Now 'req' object which extends 'defautls' about  user configuration is passed to parseNSJSON and parsePDJSON functions, so valid fields 'nearbySearchKeys' and 'placeDetailsKeys' are used to parse JSON and return what user requested"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant