You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The source for dutch realtext includes translations for gdamn and gdamned. Since we use the library to seed a acceptance that we wish to share with customers, this is not ok for us. For now the workaround is setting the locale to Flemish.
Versions
Version
PHP
8.2.13
fakerphp/faker
1.23.1
Self-enclosed code snippet for reproduction
return [
'title' => fake()->realText(),
]
Expected output
Something that does not contain profanities
Actual output
[
"title" => "Een man die geld kwam ophalen voor de Partijkas, dan gaf hij hun een sigaar op, van mij, een sigaar in z'n kamer, hardop:\"Een groot dichter zijn en dan vallen, Godverdomme.\""
]
The text was updated successfully, but these errors were encountered:
You have a proposal for something else? Thing is that is always opiniated in some sort.
You could always define your own provider foe this
I completely agree with @TomasDePomas, it's not okay - I'm not sure if the text comes from another library but if not, I would suggest something like: realText($maxNbChars = 200, $indexSize = 2, $textType = 'formal')
Being able to have a formal (or non-cursing...) text by default and being able to switch it if a non-formal text is allowed.
Summary
The source for dutch realtext includes translations for gdamn and gdamned. Since we use the library to seed a acceptance that we wish to share with customers, this is not ok for us. For now the workaround is setting the locale to Flemish.
Versions
fakerphp/faker
Self-enclosed code snippet for reproduction
Expected output
Actual output
The text was updated successfully, but these errors were encountered: