Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"keypath" does not work #17

Closed
GoogleCodeExporter opened this issue Feb 22, 2016 · 2 comments
Closed

"keypath" does not work #17

GoogleCodeExporter opened this issue Feb 22, 2016 · 2 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. make a new rule specifying a pref that is a key path
2. add path to key field, eg: "preferences/code" ("preferences" being the key 
of a main level 
dictionary, and code being the key of the value inside the "preferences" 
dictionary)
3. check the "Keypath" checkbox
4. try to use it

What is the expected output? What do you see instead?
expected: that it works
seen: it does not treat the keypath as a path, it adds a new key using the 
entire string at the root 
level

What version of the product are you using? On what operating system?
latest latest

Please provide any additional information below.
documentation would help

Original issue reported on code.google.com by anbaricf...@gmail.com on 2 Mar 2008 at 10:19

@GoogleCodeExporter
Copy link
Author

keypaths are period delimited

Original comment by j...@gmail.com on 2 Mar 2008 at 11:11

@GoogleCodeExporter
Copy link
Author

Original comment by j...@gmail.com on 2 Mar 2008 at 11:47

  • Changed state: WontFix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant