Files
website/client/test/userSafety.test.js
wtclaude 41a1e84b51
All checks were successful
PR Checks / bot-tests (pull_request) Successful in 36s
PR Checks / server-tests (pull_request) Successful in 6m11s
PR Checks / client-build (pull_request) Successful in 49s
feat(safety): report, block and hide, MODULE_API 1.21.0
USER_SAFETY.md step 2 (core), with S11-S14 decided while building it.

- Reports: POST /player/reports takes any target type, core's forum
  types or a module's registered ones. One resolver
  (model/safety/targets.js) answers "what is this item, for this
  reader" and 404s an item the reader cannot see. Every report stores
  content_reports.snapshot; the queue shows a module item from it.
- Hide for everyone: POST /admin/moderation/reports/:id/hide hides the
  item through its own moderation (forum hide as staff, or the module's
  hide) and actions the report with actioned_with = 'hide'.
- Blocks (user_blocks) name an item, never a person, and land on the
  author's account first (S12); an unlinked game identity is blocked as
  itself and becomes an account block once linked (S14). Staff cannot
  be blocked; a block on someone later promoted stops applying (S8).
- Hide for me (user_hidden_items), /auth/me/blocks and /auth/me/hidden.
- Forum reads filter blocked authors and hidden items on the server and
  carry canBlock per thread and post.
- MODULE_API 1.21.0: api.registerReportTargets,
  api.registerGameIdentities, ctx.safety.forViewer and
  ctx.safety.staffAmong, so a module filters its own per-viewer feeds on
  the server (S11) and marks lines canBlock (S13).
- Web: Hide for me / Block author in the forum menus, a Blocked section
  on both account pages, Hide for everyone in the Reports queue.
- Tests, OpenAPI, route/guard/engagement manifests regenerated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
2026-10-30 05:41:00 -05:00

25 lines
1.4 KiB
JavaScript

// Account → Blocked and the Reports queue's "Hide for everyone"
// (client/src/lib/userSafety.js; docs/website/USER_SAFETY.md §1, §4.1).
import { test } from 'node:test'
import assert from 'node:assert/strict'
import { blockSubtitle, canHideForEveryone } from '../src/lib/userSafety.js'
test('a game block says it is a Steam id with no account yet; an account block says Account', () => {
const game = blockSubtitle({
kind: 'game',
identity: { module: 'rust', kind: 'steam', label: 'Steam account', id: '76561198000000123' },
})
assert.equal(game, 'Steam account 76561198000000123, not linked to an account')
assert.equal(blockSubtitle({ kind: 'account', identity: null }), 'Account')
assert.match(blockSubtitle({ kind: 'account', createdAt: '2026-10-30T10:00:00Z' }), /^Account · blocked /)
})
test('hide for everyone is offered on a post, a thread and a chat line, never on an upload or twice', () => {
assert.equal(canHideForEveryone({ targetType: 'team_forum_post', actionedWith: null }), true)
assert.equal(canHideForEveryone({ targetType: 'team_forum_thread', actionedWith: null }), true)
assert.equal(canHideForEveryone({ targetType: 'rust.chat', actionedWith: null }), true)
assert.equal(canHideForEveryone({ targetType: 'team_forum_upload', actionedWith: null }), false)
assert.equal(canHideForEveryone({ targetType: 'rust.chat', actionedWith: 'hide' }), false)
})