New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bundle the old RegexSwap's regexes into the distribution #1767
Comments
I made a little tool to spit out some tentative output that would fit into the conf.xml format. Not great code, but works as a one-off:
|
I'm not sure it really matters, since no one ever really contributed patterns, but wouldn't RegexSwap be really easy to just dump in a GitHub Page? That way, it's also easy to contribute a pattern, just make a PR against the RegexSwap GH page repo. (of course, dynamic things like voting would not survive, but I'm not sure that's really a big loss. There's the possibility of discussing them in the repo's issues list, and improving them through a PR. This seems better than a simple voting system) |
Good point. We could even put it up on https://datacleaner.github.io somewhere, just like the new version endpoint that it has (https://datacleaner.github.io/meta/versions.json) which I intended for something similar (update notifications). |
Cool. Both separate and combined makes perfect sense, so let's go with whatever you prefer :) |
I've made the regexes available at https://datacleaner.github.io/content/regexes.json |
Or for source code access: https://github.com/datacleaner/datacleaner.github.io/blob/master/content/regexes.json |
It seems to me that they're not very well maintained though. I'm gonna do a bit of cleanup in the descriptions and such, but I'm sure more people than me can help too, so let this be an open invite to any contributor to pitch in with their good regex contributions :-) |
Now that RegexSwap is no longer available, should we just put all those regexes into the application itself?
I've gone ahead and queried the regexes just to be able to preserve them for future use:
The text was updated successfully, but these errors were encountered: