Vishnu Ks 553c50ebfb messages: Add history_limited flag to messages response. ... The purpose of this commit is to pass information to the frontend whether the message response recieved has been limited due to plan restrictions or not. To implement this, the backend for limiting the message history had to be rewritten as we used to fetch only the message rows whose id was greater than first_visible_message_id. The filtered rows gives us no information on whether the message history was limited or not. So the backend was rewritten to not do any restriction of limiting the message rows while making the query. The limiting of rows is now done in post_process_limited_query which will also return back the value of history_limited flag. Tweaked by tabbott to note a few cases where the results are incorrect. I'm merging this despite those, because those cases don't impact the correctness of the feature, and it may have tricky performance implications to fix correctly.		2018-10-26 17:41:07 -07:00
..
zulip-2.0.yaml	api docs: Document the /dev_fetch_api_key endpoint.	2018-10-16 12:47:12 -07:00
zulip.yaml	messages: Add history_limited flag to messages response.	2018-10-26 17:41:07 -07:00