f62f8c9238
Overall, this change eliminates a lot of optional parameters and conditionals, plus some legacy logic related to caches. For all the places we are just editing topics, we now just call `check_topic` to see that the topic got updated. For places where the topic edit failed, we just inline the checks that message still has the old topic and content. And then for successful **content** edits, we now do a more rigorous, more sane check that the messages are properly cached. The old code here had evolved from 2013 into something that didn't really make much sense in the context of editing topics. Now we are literally pulling data from the cache and making sure it's valid, rather than trying to poorly simulate the two codepaths related to dispatching message events and fetching messages. Some of the history here was that when I introduced `MessageDict` several years ago, I did a lot of code sweeping and didn't analyze every single test to make sure it's still valid, plus some of the tests still had some value for catching regressions. A recent commit now gets us coverage on that a lot more explicitly, rather than in passing. |
||
---|---|---|
.circleci | ||
.github | ||
.tx | ||
analytics | ||
confirmation | ||
corporate | ||
docs | ||
frontend_tests | ||
locale | ||
pgroonga | ||
puppet | ||
requirements | ||
scripts | ||
static | ||
stubs | ||
templates | ||
tools | ||
zerver | ||
zilencer | ||
zproject | ||
zthumbor | ||
.browserslistrc | ||
.codecov.yml | ||
.editorconfig | ||
.eslintignore | ||
.eslintrc.json | ||
.gitattributes | ||
.gitignore | ||
.gitlint | ||
.isort.cfg | ||
.npmignore | ||
.stylelintrc | ||
.travis.yml | ||
.yarnrc | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
Dockerfile-postgresql | ||
LICENSE | ||
NOTICE | ||
README.md | ||
Vagrantfile | ||
babel.config.js | ||
manage.py | ||
mypy.ini | ||
package.json | ||
postcss.config.js | ||
tsconfig.json | ||
version.py | ||
yarn.lock |
README.md
Zulip overview
Zulip is a powerful, open source group chat application that combines the immediacy of real-time chat with the productivity benefits of threaded conversations. Zulip is used by open source projects, Fortune 500 companies, large standards bodies, and others who need a real-time chat system that allows users to easily process hundreds or thousands of messages a day. With over 500 contributors merging over 500 commits a month, Zulip is also the largest and fastest growing open source group chat project.
Getting started
Click on the appropriate link below. If nothing seems to apply, join us on the Zulip community server and tell us what's up!
You might be interested in:
-
Contributing code. Check out our guide for new contributors to get started. Zulip prides itself on maintaining a clean and well-tested codebase, and a stock of hundreds of beginner-friendly issues.
-
Contributing non-code. Report an issue, translate Zulip into your language, write for the Zulip blog, or give us feedback. We would love to hear from you, even if you're just trying the product out.
-
Supporting Zulip. Advocate for your organization to use Zulip, write a review in the mobile app stores, or upvote Zulip on product comparison sites.
-
Checking Zulip out. The best way to see Zulip in action is to drop by the Zulip community server. We also recommend reading Zulip for open source, Zulip for companies, or Zulip for working groups and part time communities.
-
Running a Zulip server. Use a preconfigured Digital Ocean droplet, install Zulip directly, or use Zulip's experimental Docker image. Commercial support is available; see https://zulipchat.com/plans for details.
-
Using Zulip without setting up a server. https://zulipchat.com offers free and commercial hosting, including providing our paid plan for free to fellow open source projects.
-
Participating in outreach programs like Google Summer of Code.
You may also be interested in reading our blog or following us on twitter. Zulip is distributed under the Apache 2.0 license.