5

I've been trying to set up a filter I can use with /questions/{id}/answers/ (using the UI at this link), which returns the following fields:

answer:
    answer_id
    body_markdown
    comments
    creation_date
    owner
    score
    share_link

comment:
    body_markdown
    link
    owner

shallow_user:
    display_name
    user_id

The problem is body_markdown. No matter what I do, the filters don't return it. Sometimes they do, if I switch off some of the other fields, but even then, if I actually want to use the filter in a request, it breaks again.

For example, I created the filter: !)ayn4w2btvFUpB1d6.o.BKKcUINGse1wa_ZUcP23R8RvI .
It should contain all of the above fields and, if I query it at /filters/{filter} it reports to include all the fields I want.

But if I actually use it, either testing it in the docs or sending an actual query the comment.body_markdown field is not present.

What's going on here?

6
  • 1
    Just found this bug report from 3 months ago. Feel free to close this one as a duplicate, but I don't want to delete it, because it contains a bit more information for reproducing the bug. Commented Nov 11, 2014 at 19:53
  • 1
    This Q is better. Close the other one as a dupe of this one. (As shown on SO, multiple times, age is no factor on which Q gets called duplicate.) Commented Nov 11, 2014 at 21:41
  • 1
    Was this ever resolved? (ping @BrockAdams) It's getting really frustrating for me, having to burn two API requests whenever I want to get a question + comments or answer + comments. Commented Sep 19, 2017 at 17:18
  • 1
    @TastesLikeTurkey, no it is not resolved. The devs are very lackadaisical about API bugs. Try cross-posting a bug report on Meta Stack Exchange. Commented Sep 19, 2017 at 17:24
  • 1
    @BrockAdams Thanks. Done. Commented Sep 19, 2017 at 17:30
  • 1
    Still an issue for me. I find that when I have this problem, if I add body to the filter, run it once, then I'll get both body and body_markdown, then if I remove body, I'll get body_markdown in the next run but not any subsequent to that. It's seems like a weird caching rule or something but surely more have experienced this than the few users here? Commented May 22, 2018 at 13:58

0

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.