Skip to content

Feature/language filter#98

Draft
rmirabelli wants to merge 3 commits intoBottleRocketStudios:mainfrom
rmirabelli:feature/languageFilter
Draft

Feature/language filter#98
rmirabelli wants to merge 3 commits intoBottleRocketStudios:mainfrom
rmirabelli:feature/languageFilter

Conversation

@rmirabelli
Copy link
Contributor

Added a language filter mechanism. This will allow developers to quickly implement light client-side filtering for a selection of words that are vulgar, hateful, or disrespectful.

Anyone interested in investigating the selected list of words can do so by rot13ing against the source array, but I didn't want the list in plaintext.

Note that this will not pass CI yet, because the screenshot library's current version isn't compatible with the latest Xcode. There's an open PR for that, which I incorporated locally.

@rmirabelli rmirabelli marked this pull request as draft June 19, 2020 18:57
@BottleRocketBot
Copy link

Warnings
⚠️ No CHANGELOG entry added.

Generated by 🚫 Danger Swift against ae1236a

To find if a string contains potentially objectionable input, create a filter and place a query.

``` swift
// TODO
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like we're missing the basic how-to from here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whoops!

I guess at least I put in the todo. I wrote that before I decided how I'd implement it. :)

import UtiliKit
import XCTest

class LanguageFilterTests: XCTestCase {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well this is certainly a... unique... set of tests 😄

Copy link
Contributor

@wmcginty wmcginty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops - I think we also need to update the Podspec to define the new subspec.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants