search

remotestorage / remotestorage.js

⬡ JavaScript client library for integrating remoteStorage in apps
https://remotestoragejs.readthedocs.io
MIT License
2.33k stars 141 forks source link

problem with URI encoded keys #117

Closed nilclass closed 12 years ago

nilclass commented 12 years ago

When I use a key like Club%20Mate (e.g. created by myfavoritedrinks), when pushing it to remote everything is fine, but as soon as it get's synced back, there are two versions of the data, one called Club%20Mate, one Club Mate. I guess there is some browser magic that translates %20 to a space, need to figure out where that is.

melvincarvalho commented 12 years ago

people often replace spaces with hyphens to be more friendly, tho of course this can add an extra layer of complexity ...

nilclass commented 12 years ago

that would be possible to do in myfavoritedrinks. It just happens due to the choice of key there. But the more general problem is, that those keys aren't consistent when synchronizing between local cache <-> remotestorage. So we either need to fix that, or prevent people from using URI-encoded keys, which sucks.

melvincarvalho commented 12 years ago

No you're absolutely right, the space must be supported. Just saying that very often when naming people sometimes choose to replace, say space with -

nilclass commented 12 years ago

This is actually a bug in the storage server(s). I'm fixing it now for remotestorage-ruby.