timriley on remove-auto-register
Remove commented code (compare)
timriley on remove-auto-register
Remove no-longer-relevant doc (compare)
timriley on remove-auto-register
Remove another unneeded splat (compare)
timriley on remove-auto-register
Li’l tweak (compare)
timriley on remove-auto-register
Li’l tweak (compare)
timriley on remove-auto-register
Simplify args passed to build_f… (compare)
timriley on remove-auto-register
Further simplify args for build… (compare)
timriley on remove-auto-register
Remove `auto_register!` and add… Provide the default loader to a… Simplify args passed to build_f… (compare)
timriley on rich-component-dirs-config
Accept plain options hash inste… (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 }
Types
module you have a clash with Types::DateTime
constant