Skip to content

Fix incorrect .TypeMismatch KeyPath error reporting#121

Merged
ikesyo merged 1 commit intomasterfrom
fix-typemismatch-keypath-output
Apr 20, 2016
Merged

Fix incorrect .TypeMismatch KeyPath error reporting#121
ikesyo merged 1 commit intomasterfrom
fix-typemismatch-keypath-output

Conversation

@ikesyo
Copy link
Copy Markdown
Owner

@ikesyo ikesyo commented Apr 19, 2016

Fixes #120. The keyPath output is now keyPath: KeyPath(["dialog", "displayType"]) for that case.

/cc @toshi0383

@ikesyo ikesyo force-pushed the fix-typemismatch-keypath-output branch from b0b4af0 to 2e586cd Compare April 19, 2016 13:35
@toshi0383
Copy link
Copy Markdown

Thanks a lot😆
Just wondering. What KeyPath(["dialog", "displayType"]) means is dialog.displayType, right ?
Or is there other context meaning for KeyPath ?

@ikesyo
Copy link
Copy Markdown
Owner Author

ikesyo commented Apr 20, 2016

What KeyPath(["dialog", "displayType"]) means is dialog.displayType, right ?

It's right. 💡 KeyPath represents nested keys in a JSON object structure.

@toshi0383
Copy link
Copy Markdown

Got it !

@ikesyo
Copy link
Copy Markdown
Owner Author

ikesyo commented Apr 20, 2016

🚢

@ikesyo ikesyo merged commit 8367ac1 into master Apr 20, 2016
@ikesyo ikesyo deleted the fix-typemismatch-keypath-output branch April 20, 2016 12:55
@ikesyo ikesyo mentioned this pull request Apr 25, 2016
@ikesyo ikesyo added the bug label Apr 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants