Version:
2.2.1
Issue:
For example giving the following service call:
Service<Resource>.all({
remotefilter: {
field: "foo&bar"
}
})
The serialized URL will be:
...?filter[field]=foo&bar
which isn't correct. The work around is to manually encrypt the string before passing to the filter. This isn't very robust as the developer may forget to do so
Solution:
URL encrypt the string field (encodeURIComponent) by default and provide an option to override?