iCal says property names are case insensitive, but kcalcore doesn't
implement that. 99% of kdepim uses uppercase property names for custom
properties, which is actually consistent with other iCal properties.
Creating a project or a context and then syncing with the kolab server
would lose the fact that it was a project or context, forcing the user
to change the type of the item again (easy for a project, impossible for a context).
On the other hand this commit creates a migration problem for existingI looked a bit into fixing kcalcore's CustomProperties but calling .toUpper()
projects on non-kolab servers...everywhere sounds slow, users will have to promote alluppercasing the keys could in theory break users of
projects as such,the QMap accessor, and more importantly, is there anyone to review such a change? one time after;)
OTOH this lands.
I looked a bit into fixing kcalcore's CustomProperties but calling .toUpper()commit is how the code should have been in the first place, to
everywhere sounds slow, uppercasing the keys could in theory break users of
the QMap accessor, and more importantly, is there anyone to review such a change?be consistent with the rest of kdepim.
;)This commit includes automatic migration from "Project" to "ISPROJECT"
OTOH this commit is how so that the code should have been in the first place, tohange is transparent to users.
be consistent with the rest of kdepim.