敏感词匹配替换功能

Open
#5,166 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
backend, security

Research direction

No files, tests, or entry points are identified in the issue. Start by tracing where sensitive-word matching is currently handled and determine how users would configure replacement values. Done means configured sensitive content is replaced consistently while preserving unaffected content and protecting user privacy.

Written by the indexing model from the issue text.

Description

enhancement

您当前的 newapi 版本

v1.0.0-rc.7

提交确认

  • 我已确认目前没有类似 issue
  • 我已完整查看过文档 https://docs.newapi.ai/ 和项目 README,已确定现有版本无法满足需求
  • 我未删除此模板中的任何引导内容或小节标题,并会按要求完整填写
  • 我理解项目维护者精力有限,不遵循模板要求的 issue 可能会被无视或直接关闭

功能描述
添加匹配到敏感词时,将匹配到的内容替换为预先设置的内容。
应用场景
保护用户的隐私,用户可以自行设置想被替换的内容,如密码、号码等。

Dominant language
Go
Stars
48.5k
Forks
11.6k
Avg merge
1d 13h
Merged PRs (30d)
58

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from QuantumNous/new-api

All issues in QuantumNous/new-api

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.