3

I have run /inbox/unread function. It returns a list of inbox_items.

The body of inbox_item gives excerpt, not the full body. This is with all the functions that return inbox_item.

According to me this is a bug. Is this the expected behavior?

In case of /me/questions, body of question is coming as expected.

Improve this question

1 Answer 1

Reset to default
3

An inbox message body is not the same as a post body. Inbox messages are truncated by design.

Here's a snippet of my inbox:

inbox


Notice how the "body" is truncated at 100 characters? (Counting the ... and accounting for HTML entities like '.)

The results I get from /2.2/me/inbox?filter=!SmOhH2b13NujlyyXX6 are exactly the same:

"body": "Very good. I'm not an expert on user scripts after all. Good job.",
...
"body": "Aah, thnaks. The original answer didn't have that information (as linked) but it's quite ...",
...
"body": "@BrockAdams Ah, that's what I suspected. Sorry, I'm veering from the original question at...",
...

There is no bug here.

Improve this answer
4
  • It would be good if there was uniformity. Somewhere it is truncated, other places it is not.
    – amit jha
    Commented Jul 22, 2015 at 9:17
  • Inbox items have always been truncated so. Where is it not truncated and the source text was more than 100 characters? Show a counterexample, if you have one.
    – Brock Adams
    Commented Jul 22, 2015 at 9:37
  • I meant to say in body of inbox_items it is truncated. In body of question it is not truncated. I was taking about this uniformity.
    – amit jha
    Commented Jul 22, 2015 at 9:52
  • It's apples and oranges. They both are called "body" but they are not the same thing. It's rather like you should "cleave" to your wife, but you should never "cleave" her in two (unless the {censored} is asking for it). Same word, two very different things.
    – Brock Adams
    Commented Jul 22, 2015 at 10:38

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .