mattermost/server/channels
2026-04-06 18:32:13 +03:00
..
api4 Merge branch 'master' into mm-68129 2026-04-04 21:38:08 +02:00
app Added nil checks (#35755) 2026-04-06 08:47:24 +05:30
audit [MM-64686] Expose audit logging functionality via plugin API (#31204) 2025-06-25 20:37:32 -04:00
db simplify CODEOWNERS (#35770) 2026-04-01 13:03:36 +00:00
doc/help Mono repo -> Master (#22553) 2023-03-22 17:22:27 -04:00
jobs upgrade golangci-lint (#35845) 2026-03-30 13:41:32 -03:00
manualtesting MM-28765: Fix errcheck issues in server/channels/manualtesting/manual_testing.go (#30613) 2025-04-09 11:41:56 +02:00
store MM-68158: Fix shared channel remote display and notify UI on invite completion (#35908) 2026-04-03 02:06:01 -04:00
testlib Merge the Integrated Boards MVP feature branch (#35796) 2026-03-27 10:36:35 +01:00
utils Fix import failures for Japanese filenames with dakuten on macOS (#35204) 2026-03-18 12:16:55 +00:00
web upgrade golangci-lint (#35845) 2026-03-30 13:41:32 -03:00
wsapi Add audits for accessing posts without membership (#31266) 2026-01-20 10:38:27 +01:00
README.md simplify CODEOWNERS (#35770) 2026-04-01 13:03:36 +00:00

Server Channels Review Guidelines

When reviewing or writing code in the server channels package, focus on SQL query performance and API layer efficiency.

SQL Store Layer

  • Run EXPLAIN ANALYZE on new or modified queries against a large dataset before merging. A query that performs well on a 12M-post database may degrade significantly at 100M+ posts.
  • Watch for sequential scans on large tables. Ensure appropriate indexes exist for new query patterns.
  • When adding new queries to the store, check whether an existing query already fetches the needed data. Avoid duplicate round trips to the database.

API Layer

  • Minimize database round trips. If an endpoint calls a Get followed by a Delete on the same row, consider using DELETE ... RETURNING to combine them into a single query.
  • Don't add queries that are unnecessary for the operation. The most efficient work is the work you don't do.
  • When adding new API endpoints, add them to the load test tooling so performance can be validated under realistic concurrency.

Permissions and Security

  • Verify that new endpoints enforce appropriate permissions. Rely on the dedicated security review for thorough coverage, but flag anything obviously missing (e.g., an endpoint that skips permission checks entirely).