It also defines the instance predicates past?, today?, tomorrow?, next_day?, yesterday?, prev_day? and future?, all of them relative to Time.current. That's like Time.now, except that it honors the user time zone, if defined. If since or ago jumps to a time that can't be expressed with Time a DateTime object is returned instead.Īctive Support defines Time.current to be today in the current time zone.The instance predicates past? and future? are defined relative to DateTime.current. beginning_of_hour / at_beginning_of_hourġ6.1.1 Named Datetimes 16.1.1.1 DateTime.currentĪctive Support defines DateTime.current to be like _datetime, except that it honors the user time zone, if defined.The following methods are only implemented in active_support/core_ext/date_time/calculations.rb as they only make sense when used with a DateTime instance: On the other hand, advance and change are also defined and support more options, they are documented below. beginning_of_day / midnight / at_midnight / at_beginning_of_day.The following methods are reimplemented so you do not need to load active_support/core_ext/date/calculations.rb for these ones: The class DateTime is a subclass of Date so by loading active_support/core_ext/date/calculations.rb you inherit these methods and their aliases, except that they will always return datetimes. For example seconds_since_midnight might not return the real amount in such a day. This means Date.today may equal Date.yesterday.ĭateTime is not aware of DST rules and so some of these methods have edge cases when a DST change is going on. There are cases where the user time zone might be in the future compared to the system time zone, which Date.today uses by default.
When making Date comparisons using methods which honor the user time zone, make sure to use Date.current and not Date.today. It also defines Date.yesterday and Date.tomorrow, and the instance predicates past?, today?, tomorrow?, next_day?, yesterday?, prev_day?, future?, on_weekday? and on_weekend?, all of them relative to Date.current. That's like Date.today, except that it honors the user time zone, if defined. 15.1.1 Date.currentĪctive Support defines Date.current to be today in the current time zone. Please check test/core_ext/date_ext_test.rb in the Active Support test suite for expected behavior. This guide does not document their behavior around those days for brevity, but it is enough to say that they do what you would expect. The following calculation methods have edge cases in October 1582, since days 5.14 just do not exist. Unless the option :skip_types exists and is true, an attribute "type" is added as well according to the following mapping: If value is nil an attribute "nil" set to "true" is added. Otherwise, a node with key as tag is created with a string representation of value as text node. If value responds to to_xml the method is invoked with key as :root. Depending on the arity, the callable is invoked with the options hash as first argument with key as :root, and key singularized as second argument. If value is a callable object it must expect one or two arguments. If value is an array there's a recursive call with key as :root, and key singularized as :children. If value is a hash there's a recursive call with key as :root. To do so, the method loops over the pairs and builds nodes that depend on the values. If there's any element that does not belong to the type of the first one the root node becomes "objects": In the example above that's "contributors". All items must respond to to_xml, an exception is raised otherwise.īy default, the name of the root element is the underscored and dasherized plural of the name of the class of the first item, provided the rest of elements belong to that type (checked with is_a?) and they are not hashes. To do so it sends to_xml to every item in turn, and collects the results under a root node.
to_xml # => # 4356 # Jeremy Kemper # 1 # jeremy-kemper # 4404 # David Heinemeier Hansson # 2 # david-heinemeier-hansson # Copy
0 kommentar(er)
