#shortcuts for javascript

I have been working on a new app and as it tends to happen, a routine requirement (parsing user input) quickly became a 2 day conundrum. 

I considered the parsing task complete over the weekend and rewarded myself with a swim in the ocean and a delicious IPA. But then... 

All hail/Ah hell... User Input! 

As a quick reference/aside, User Input is like the hair of my sister’s high school boyfriend – unpredictable and sometimes unkempt (see: 80′s Jon Bon Jovi).

Over the past few mornings (mornings start proportionately earlier as a task becomes a roadblock), I hit a wall trying to figure out how to simply get around a common task:

Task: Split user input by multiple common separators: commas, tabs, spaces, linebreaks/returns, semicolons, colons (some people are into that) Example: User enters names: Tom Tomato, Tim Tomillio, Todd Thoas Solution: Javascript’s handy Split() Method Output As:  • Tom Tomato • Tim Tomillio • Todd Thoas

Easy enough.

“But wait”, my wife seems to eagerly point out, “What if I want to enter a formal name that includes a shortened version or a nickname... like yours?” F. Touché ladybird, touché. 

Okay, so shouldn’t be that hard: 

Updated Task: Modify the parser to account for common ways people type these out.  Example: Thomas (Tom, Tmoney), Timothy (Tim Timmy), Todd (Toodles)  Solution: ... many attempts ... many failures. 

What’s the issue? 

Todd (Toodles), – None. Passes easily. The match finds the comma and separation is correct.

Timothy (Tim Timmy), – One. The space after “(Tim” is causing “Timmy)” to output separately. So we remove the option in our split of separating User Input by spaces, the match finds the comma and separation is correct. Sweet.

Thomas (Tom, Tmoney), – One and it becomes a bricklayer. The match ignores the space between “(Tom,” and “Tmoney),” – so that is a success. However, the match finds the comma between "(Tom”, and “Tmoney)” and outputs “Thomas (Tom’ and “Tmoney)” separately. Turns out, this is the jackleg.

So what is the issue?

Commas in development are cunning Linguists!

Commas are one of the (if not the most) common separators in the history of User Input. This is not based on facts, but more a logical assumption. So they are here to stay. 

This led to a series of clever attempts, scientific regular expression theory, work-around hacks, brute force, and finally a resolve thanks to the brilliant mind of this regex genius who was kind enough to help someone who was in a similar situation.

Avinash’s Regex Solution:

,(?![^()]*(?:\([^()]*\))?\))

His Regex Explanation:

// ,            ',' // (?!          look ahead to see if there is not: //   [^()]*     any character except: '(', ')' (0 or more times) //   (?:        group, but do not capture (optional): //     \(       '(' //     [^()]*   any character except: '(', ')' (0 or more times) //     \)       ')' //   )?         end of grouping, ? after the non-capturing group makes the whole non-capturing group as optional. //   \)         ')' // )            end of look-ahead

His Example on Regex101 His Answer on Stack Overflow

The implementation that works for my particular brickhouse:

Tired of making those year updates? Add this where the year is in the footer and you won’t have to update those manually √ 

Example: © 2015 Company Name. == Static

Example: © <script>document.write(new Date().getFullYear())</script> Company Name. == Dynamic. Works on all browsers without additional libraries required.

<script>document.write(new Date().getFullYear())</script>

This is a simple pure JS oldie, but a huge time saver. I’m reminded/thankful for this single line of code a few months before the new year, because January (at least for our corporate sites) means tons of requests for copyright updates across thousands of websites, landing pages, digital files, etc.