4dc1b2f812
We refactor the triage function to optionally take in a comparator function, and use this to sort the results, except any exact match, which is placed highest. Now we don't need to sort the results of triage for streams, languages and slash commands since we just pass in the comparator function. The overall effect is same as before, except that exact matches are always shown first. For users, we can't use the new triage feature to achieve this goal without sorting `rest` and breaking a key optimization, so we just add a bit of manual code for the job. Fixes: #25123. |
||
|---|---|---|
| .. | ||
| icons | ||
| src | ||
| tools | ||
| .gitignore | ||
| .npmrc | ||
| README.md | ||
| package.json | ||
| tsconfig.json | ||
README.md
The files in this subtree are part of the Zulip web frontend, and are also incorporated by the Zulip mobile app.
Note that the deployment cycles are different:
-
In the web app, this code is deployed in the same way as the rest of the web frontend: it's part of the server tree, and the browser gets it from the server, so the client is always running the same version the server just gave it.
-
In the mobile app, this code is deployed in the same way as the rest of the mobile app: it's bundled up into the app binary which is uploaded to app stores and users install on their devices. The client will be running the version built into their version of the mobile app, which may be newer, older, or simply different from the version on the server.
The mobile app always refers to a specific version of this code; changes to this code will appear in the mobile app only after a commit in the mobile app pulls them in.
To update the version of @zulip/shared on NPM, see the instructions in the mobile repo.