Add supports for custom replacer

[halkeye]

super related to #168

Allows custom regexes to be applied.

[TimonVS]

Thanks for your contribution @halkeye 🙇‍♂️. I left some minor feedback but overall it looks good to me 🙂.

[jetersen]

Looks good so far, I have a few concerns

[halkeye]

Okay, thanks for the review, I think i got everything brought up handled.

[halkeye]

travis needs a retry

[toolmantim]

Thanks so much @halkeye — looks great! 👌🏼 First PR too! 🎉

I have some readme edits, and then we're good to go.

[halkeye]

Thanks for all the comments and suggestions @toolmantim

I think i addressed them all, as well as fought with the master merge, so I think its ready to go again.

[toolmantim]

Thanks for the updates, you’re awesome! 🎉🎉🎉🎉

[halkeye]

:D SO EXCITED

How often do you release it to the actual github app? when can i start using it?

[toolmantim]

When the new npm package gets released, it gets deployed to match. I think the only thing we need to check is whether @TimonVS reckons we should add #188 beforehand?

[TimonVS]

I'm leaning towards adding the sorting option first because we're changing the default sorting direction which might be confusing to users. But I don't have a strong opinion about it so I'll leave the decision to you @toolmantim, I'll probably have some time tomorrow to start implementing the sorting option :)

[jetersen]

cheeky beep 😆 I spent an hour thinking my schema addition was borked when in reality you modified the schema. 😡 At myself for not reading the code more closely before deleting it 😆