mirror of https://github.com/zulip/zulip.git
1ac8fe7538
We send the whole data set as a part of the event rather than
doing an add/remove operation for couple of reasons:
* This would make the client logic simpler.
* The playground data is small enough for us to not worry
about performance.
Tweaked both `fetch_initial_state_data` and `apply_events` to
handle the new playground event.
Tests added to validate the event matches the expected schema.
Documented realm_playgrounds sections inside /events and
/register to support our openapi validation system in test_events.
Tweaked other tests like test_event_system.py and test_home.py
to account for the new event being generated.
Lastly, documented the changes to the API endpoints in
api/changelog.md and bumped API_FEATURE_LEVEL.
Tweaked by tabbott to add an `id` field in RealmPlayground objects
sent to clients, which is essential to sending the API request to
remove one.
|
||
|---|---|---|
| .. | ||
| curl_param_value_generators.py | ||
| javascript_examples.js | ||
| javascript_examples.py | ||
| markdown_extension.py | ||
| openapi.py | ||
| python_examples.py | ||
| test_curl_examples.py | ||
| testing.yaml | ||
| zulip.yaml | ||