Realised that my date/time modules were using unsafe string parsing for formats.
10 minutes later, thanks to @propensive 's contextual, I'm enjoying compiler checked date/time format literals.
-
-
Don’t even bother with the license, that’s pretty much the same code as contextual’s most basic example. I can maybe license the bespoke serializable format wrapper, but you have no interest in that.
1 reply 0 retweets 0 likes -
Replying to @NicolasRinaudo @fommil
I should release the latest version of Contextual some time which reduces that example to a single method invocation... on my todo list for today.
1 reply 0 retweets 0 likes -
Replying to @propensive @fommil
I'm all for that, especially since I intend to write at least another interpolator in the near future!
1 reply 0 retweets 1 like -
Replying to @NicolasRinaudo @fommil
Version 1.1.0 is on its way to Maven Central. It's anything up to a couple of days from now, based on past form...
1 reply 0 retweets 0 likes -
Replying to @propensive @fommil
O ye, of little faith https://search.maven.org/#artifactdetails%7Ccom.propensive%7Ccontextual_2.11%7C1.1.0%7Cjar …
1 reply 0 retweets 1 like -
Now, without meaning to sound too ungrateful, I think you might have forgotten to update the documentation :)
1 reply 0 retweets 1 like -
Replying to @NicolasRinaudo @fommil
Oh, I haven't forgotten... it's just a bigger job, unfortunately...
1 reply 0 retweets 0 likes -
Replying to @propensive @fommil
Ah, right. But would it be possible to write a quick gist showing off the simplifications you brought? Right now, the `data` module still appear to use he old scheme
1 reply 0 retweets 0 likes -
Replying to @NicolasRinaudo @fommil
Oh, check out the email example. IIRC think that demonstrates it!
2 replies 0 retweets 0 likes
So, yes, quite a bit smaller and easier to understand: https://github.com/nrinaudo/kantan.codecs/blob/4814c422141fd320fdad1208677576ba5ae33edb/joda-time/core/src/main/scala/kantan/codecs/strings/joda/time/FormatVerifier.scala …
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.