afba77300a
So far, when ordering typeahead suggestions, any query matches that did not occur at the start of the target string were considered equally. So for example, for the query "ok", "squared_ok" and "smoking" were allotted equal priority, which does not make sense. Now, matches from a word boundary (space, hyphen, underscore or slash) are given priority (after exact matches and beginning matches), so that in the above example, "squared_ok" is regarded as a better match than "smoking". Since recipients' sorting is complex, and needs word boundary matches separately for decoupled sorting post triage, `triage_raw` is extracted from `triage` to return the raw matches. Fixes: #24127. |
||
|---|---|---|
| .. | ||
| 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.