Issue #15774 has been updated by oleynikov (Alexander Oleynikov).


You need to `require 'optparse/time'` to use built-in Time conversion (it doesn't seem to be stated explicitly in the documentation, but it is demonstrated throughout the examples) and you need to `require 'optparse/date'` to use Date or DateTime conversions. Or you can define custom conversions.

----------------------------------------
Bug #15774: OptionParser doesn't accept Date options as stated in the docs
https://bugs.ruby-lang.org/issues/15774#change-77719

* Author: rosenfeld (Rodrigo Rosenfeld Rosas)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.6.2p47 (2019-03-13 revision 67232) [x86_64-linux]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
The documentation for OptionParser states that Date, Time and DateTime are supported types for automatic coertion, however, it raises an error if any of those types are provided to the "on" method: "unsupported argument type: Date".

Either the documentation is wrong or there's a bug in the implementation of OptionParser I guess.

Thanks for taking a look into this.



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>