that worked! I took me a while to understand who to reproduce that in the
browser now, until I wrapped the query in quotes:
$.ajax({
url: '/test/_changes?"filter=_design%2fa%2fb/test"',
contentType: 'application/json'
})
It also works without the leading _design %2fa
$.ajax({
url: '/test/_changes?"filter=a%2fb/test"',
contentType: 'application/json'
})
Passing JSON as the query did the trick as well
$.ajax({
url: '/test/_changes?\'{"filter":"a%2fb/test"}\'',
contentType: 'application/json'
})
didn't even need to make it valid JSON
$.ajax({
url: '/test/_changes?"{filter:a%2fb/test}"',
contentType: 'application/json'
})
wow, all of the sudden it's hard to find something that does not work.
Do you know if all these are supported on purpose? Or should I rather stick
with passing valid JSON as String to assure future compatibility?
--
Gregor Martynus
On Thursday, 21. June 2012 at 22:55, CGS wrote:
> Try this:
>
> curl -X GET http://127.0.0.1:5984/test/_changes -d
> '{"filter":"_design%2fa%2fb/test"}' -H 'Content-Type: application/json'
>
> CGS
>
>
>
>
> On Thu, Jun 21, 2012 at 7:43 PM, Gregor Martynus <[email protected]
> (mailto:[email protected])>wrote:
>
> > no luck … does it work for you?
> >
> > --
> > Gregor Martynus
> >
> >
> > On Thursday, 21. June 2012 at 19:02, CGS wrote:
> >
> > > Try encoding all the slashes.
> > >
> > > CGS
> > >
> > >
> > >
> > >
> > > On Thu, Jun 21, 2012 at 4:29 PM, Gregor Martynus <[email protected]
> > > (mailto:[email protected])(mailto:
> > [email protected] (mailto:[email protected]))>wrote:
> > >
> > > > When I create a _design doc with a / in it, I'm not able to refer to
> > its
> > > > filter in the _changes feed.
> > > >
> > > > Example _design doc:
> > > > {
> > > > "_id": "_design/a/b",
> > > > "filters": {
> > > > "test": "function(doc) { return true; };"
> > > > }
> > > > }
> > > >
> > > >
> > > > _changes request:
> > > > GET http://localhost:5984/test/_changes?filter=a%2fb/test
> > > >
> > > >
> > > > returns a 400 with the body:
> > > > {
> > > > error: "bad_request",
> > > > reason: "filter parameter must be of the form `designname/filtername`"
> > > > }
> > > >
> > > >
> > > >
> > > > Is this a bug? Or am I doing something wrong?
> > > > I test it without the / in the _design doc, it worked without a problem
> > > >
> > > > --
> > > > Gregor Martynus
> > > >
> > >
> >
> >
>
>
>
