I've tracked this issue down to a mismatch in string storage formatting
between QSettings (used in unity-scopes-shell) and glib (used in unity-
api).
After some discussion with the team, I think the best way forward would
be to standardise on one ini parser across the board. I.e. update unity-
scopes-shell to use glib via unity-api's IniParser interface.
This way, what goes in, will come out.
** No longer affects: unity-api (Ubuntu)
** Also affects: unity-scopes-shell (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity-scopes-shell (Ubuntu)
Status: New => In Progress
** Changed in: unity-scopes-shell (Ubuntu)
Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-api in Ubuntu.
https://bugs.launchpad.net/bugs/1552082
Title:
String settings with special characters become quoted
Status in unity-js-scopes:
Invalid
Status in unity-scopes-shell package in Ubuntu:
In Progress
Bug description:
I'm unsure if this is a bug in the JS scopes or in scopes themselves,
but a string setting that has special characters entered into it (like
`=`) end up being surrounded by quotes when pulled in the code. For
example I have a string setting that I entered `abc=abc`, the result
in the code is `"abc=abc"`. I find this behavior to be very odd and
unexpected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-js-scopes/+bug/1552082/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
