dry-bot on master
[devtools] sync (compare)
dry-bot on master
[devtools] sync (compare)
dry-bot on master
[devtools] sync (compare)
dry-bot on master
[devtools] sync (compare)
dry-bot on master
[devtools] sync (compare)
dry-bot on master
[devtools] sync (compare)
dry-bot on master
[devtools] sync (compare)
dry-bot on master
[devtools] sync (compare)
timriley on support-component-dirs-with-mixed-namespaces
Fix rubocop issue (compare)
timriley on support-component-dirs-with-mixed-namespaces
Add Identifier docs Fix rubocop issues Add coment (compare)
Types::Strict::DateTime
initialisation. When I use the "raw" Gem-supplied types to define everything, all is well; when I use a self-defined module constant, I get a NoMethodError
running what looks like the exact same code. Gist with short single-source-file demo code here
DateTime.now
works when using Types::Strict::DateTime.default { DateTime.now }
; it does not work when attempting to use a constant defined as Types::Strict::DateTime.default { DateTime.now }