Skip to content
This repository has been archived by the owner on Dec 4, 2018. It is now read-only.

Clean test files? #120

Open
sanjaykbhat opened this issue Feb 1, 2017 · 7 comments
Open

Clean test files? #120

sanjaykbhat opened this issue Feb 1, 2017 · 7 comments

Comments

@sanjaykbhat
Copy link

The current test file : JSONStream\ test\ fixtures\ all_npm.json has profanity words: brainfuck, gang-bang etc. Do we really need these profanity words? Can we not remove them?

@dominictarr
Copy link
Owner

Well, I never intentionally put those words in, I just generated a test file from the modules on npm, where those modules are published. So, no, we don't need those "profanity" words, we just need file to test against.

https://www.npmjs.com/package/brainfuck is actually a real thing - it's an esoteric programming language with some interesting features, but I agree the gang-bang module name is in poor taste.

Why did this come to your attention? does your company have a script which searches their code & dependencies for profanity?

If you really want to, and make a pull request to remove them, I guess I'll merge it but this does seem rather unnecessary to me (especially considering that it's just in the tests, and won't get shipped to a client even if you browserify it)

@syabro
Copy link

syabro commented Feb 2, 2017

@dominictarr it's some kind of troll, please have a look at his other request
yapstudios/YapDatabase#388

@dominictarr
Copy link
Owner

Normally trolls are doing it for fun! (aka "lulz") That I can understand.
This particular "troll" doesn't seem that funny though

@sanjaykbhat
Copy link
Author

sanjaykbhat commented Feb 4, 2017 via email

@dominictarr
Copy link
Owner

@sanjaykbhat what code scanner do you use?

@sanjaykbhat
Copy link
Author

sanjaykbhat commented Feb 6, 2017 via email

@dominictarr
Copy link
Owner

so - you are asking me to change my open source software because of an mostly imagined problem created by a internal tool that isn't even open source. If your script was open source I might consider it (the open source street runs both ways! - tell your boss!)

Though, I imagine in many companies simply publishing a thing as open source isn't simply allowed, unfortunately. If this is the case for you, I might suggest updating the script to simply delete the files that contain the "offensive" words. Since in this case, it's just test files in your dependencies, it's not gonna break anything.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants