|Number of watchers on Github||37|
|Number of open issues||1|
|Open pull requests||0+|
|Closed pull requests||0+|
|Last commit||almost 4 years ago|
|Repo Created||over 8 years ago|
|Repo Last Updated||over 2 years ago|
|Organization / Author||alokmenghrajani|
|Do you use riskybird? Leave a review!|
|View riskybird activity|
|View on github|
|Book a Mock Interview With Me (Silicon Valley Engineering Leader, 100s of interviews conducted)|
Software engineers: It's time to get promoted. Starting NOW! Subscribe to my mailing list and I will equip you with tools, tips and actionable advice to grow in your career.
Regular expression authors best friend
Regular Expressions are notoriously hard to get right. When you are writing a new expression, it is hard for reviewers to read & assert with confidence that the expression is correct. Tweaking existing expressions can often lead to unintended consequences.
RiskyBird tries to mitigate this by offering a set of tools for software engineers:
This project also provides a reusable regular expression parser.
We love AngryBirds and we wanted a name that starts with R.
I haven't found a nice place to put these, so leaving these notes here.
Here are some tips to help you write better regular expressions:
Is the language regular(*)? We have often tried to write regular expressions for languages which are not regular! This always leads to issues down the road. If the language is not regular, you will need to use a Lexer/Grammar.
(*) regular expression engines actually implement some features which cannot be described by regular languages (in the formal sense), but you get my point.
Can I use a less powerful but faster library (i.e. pattern matching instead of regular expressions)?
Am I trying to match a URI (or part of one)? It is extreemly hard to get URI parsing right, and different browsers interpret URIs differently. The only way to get this right is to split the URI into parts (protocol, user, password, domain, port, path, etc.), run the desired checks on the parts and then rebuilt a new URI with the proper escaping applied to each part. Again, we have libraries to do this!
If you aren't convinced this is required, go read the browser security handbook or the Tangled Web.
Don't be lazy. If you know your expression should match the beginning of a string put the ^ anchor. If you
are expecting a
., use . instead of the dot metacharacter. Use non capturing groups when you don't need
to capture a group. Etc.
Different engines / different programming languages behave in slightly different ways (what were you expecting?). Don't just copy paste regular expressions from one language in to another!
RiskyBird is distribtued under the AGPL license.