Construire un filtre de profanités
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by locating the backend entry points that create and modify publications, then trace how title and description are validated. Compare suitable open-source profanity lists for generic English and French variants, and clarify whether matches should be rejected, flagged, or transformed. Done means the agreed behavior is applied consistently during both creation and modification.
Written by the indexing model from the issue text.
Description
Pour le moment le backend n'a aucune vérification des termes employé lorsque l'on crée une annonce. Il serait intéressant de pouvoir identifier certains mots ou phrases contenant des profanités connus et identifiable.
Ce filtre pourrait être appliqué au titre et à la description d'une nouvelle publication, autant à la création qu'à la modification.
Plusieurs liste de profanités sont disponible en ligne comme projet open-source, il faudrait en trouver une anglophone et une francophone potentiellement français-Canada, français-France et anglais-Générique.
- Dominant language
- C#
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ApplETS/Backend-Hello
-
:1st_place_medal: good first issue :cowboy_hat_face: refactor :roller_coaster: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ApplETS/Backend-Hello#78 ·
-
:1st_place_medal: good first issue :cowboy_hat_face: refactor :scroll: documentation
Difficulty 5/5 Over a week Newbie friendliness 35/100
ApplETS/Backend-Hello#76 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
ApplETS/Backend-Hello#75 ·
-
:1st_place_medal: good first issue :roller_coaster: enhancement
Difficulty 4/5 3-5 days Newbie friendliness 55/100
ApplETS/Backend-Hello#74 ·
-
:roller_coaster: enhancement
Difficulty 5/5 Over a week Newbie friendliness 28/100
ApplETS/Backend-Hello#73 ·
All issues in ApplETS/Backend-Hello
Similar issues
-
bug front-end social
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gameguild-gg/gameguild#1237 ·
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/microsoft-ui-xaml#12515 · 1 comment · 1 reaction ·
Maintainers usually reply within 2 days
-
[v5-preview5] `func new` displays incorrect command in error message when project is not initializedOpenNeeds: Triage (Functions) v5 v5-preview5
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Azure/azure-functions-core-tools#5838 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
customer-reported needs-team-triage question server-Azure.Mcp tools-Pricing
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/mcp#4087 · 1 comment ·
Maintainers usually reply within 1 day