Nicholas Chmielewski

Maybe you want to update this message....or even just keep it the same: https://github.com/radar/chronic/pull/8/commits/331be2ee32bd2e2ee6fa987fa89703c9272e72dd#diff-affb4166f690f86c30de33812976d2aaR7

If a partial changes, so will the output of the resulting ERB, which will change the SQL and trigger a reload.

That being said, would something like this be more ammenable (would extended this out to call conversion functions) https://github.com/bitwalker/timex/compare/master...hackling:ambiguity-errors?expand=1

The reason this PR came about was because we were initially using strings as IDs and it was causing all sorts of issues. While I think that it can be...

Just got back from a month holiday. Will have a look at this once I've been back behind the keyboard for a while and in a proper frame of mind....

I haven't had a chance yet. Had a few major deadlines lately, however this is on the list of things to fix and review as it's come up in development...

Sorry, I've been away on holiday. Currently it does nothing to handle really large output. That's not to say that it couldn't be updated to do so. I also have...

It would have to involve something like evaluating the composed matcher, and then if it evaluates to true, maybe override the content of the hashes so that it doesn't trigger...