High-Performance Open-Source Archive
New function get_interval_duration() which returns
the number of days covered by an element of a grates object, e.g. the
following is TRUE
identical(
get_interval_duration(yearmonth(2020, 1:3)),
c(31, 29, 31)
)as.double() for <grates_int_period>
objects now returns the same result (subject to type) as
as.integer(). Both return the lower bound of related
interval. Note that <grates_int_period> objects
should still be treated as experimental for the time being.For isoweek/epiweek/yearweek scales users can now use labels in
the form “YYYY” (e.g. 2020) without them first being converted to the
corresponding gregorian calendar representation. This can be achieved
with the argument format = "year", i.e.
`+ scale_x_grates_isoweek(format = "year")`The default offset argument for the Date and POSIXt
methods of the as_period() generic is now set as the
minimum of the input argument. Motivated by discussion with 1.
For as_period() methods, offset can now
be passed as a character or factor value that is coercible to a Date.
Again motivated by discussion with
is.numeric() now returns FALSE for all
grates objects. This makes the underlying implementation more opaque to
end users and feels more consistent with other behaviour
(e.g. no/limited support for “Math” methods).yearweek and yearmonth
objects.scale_x_grates_period() can now handle a
date value for offset.The format argument of the scale functions for
<grates_yearweek>,
<grates_epiweek> and
<grates_isoweek> can now be set to “week” to drop the
year value from graph labels, i.e.
plot + scale_x_grates_epiweek(format = "week")<grates_int_period>
object and associated scale function. This functionality should be
viewed as experimental for the time being and is marked as such in the
documentation.All images in the vignette now have alt text.
Minor documentation improvements.
New functions date_start() and
date_end() for accessing the boundary elements of
<grates> objects.
New function %during% for testing whether a scalar
date is contained within the range (inclusive) of a
<grates> object.
scale_x_grates_isoweek())
gain a breaks argument to allow exact specification of
breaks.For the first major release of grates a significant refactor has been undertaken that builds upon lessons learnt over the last two years. Whilst we have tried to limit breaking changes some functionality has been removed and some function parameters altered (see details below):
<grates_month> objects are now always stored
relative to the UNIX epoch. This is equivalent to setting
origin = 0 in the previous release. Calling the function
with an origin argument will now error.
Trying to create a <grates_month> object with
n set to 1 will now error. Uses are encouraged to use
<grates_yearmonth> for this case.
<grates_int_period> is now a defunct as it did
not fit with the scope of the package (i.e grouped dates, not grouped
integers). In particular the int_period(),
as_int_period() and is_int_period() will now
error on use.
The origin parameter from
<grates_period> as been renamed to
offset to better reflect its usage. Users will need to
update uses of period(), as_period() and
scale_x_grates_period() to reflect this.
as_yearweek() no longer parsers character strings of
the form “YYYY-Www” (e.g. “2020-W01”).
Constructors yearweek() and isoweek()
and epiweek() now allow construction of grates objects
directly from year and week integer vectors. yearmonth()
and yearquarter() constructors have been similarly changed
to allow construction from year and month/quarter integer
vectors.
The old incarnation of direct constructors now begin with a
new_ prefix (e.g. new_month(),
new_yearweek(), new_epiweek(), …). This is to
distinguish them from more user friendly constructors that we have
introduced (see above).
A new yearmonth class
(<grates_yearmonth>) and associated functions have
been introduced. This object is similar to what was previously obtained
via a call of month(x, n = 1L, origin = 0L) (now defunct -
see above).
New isoweek and epiweek classes
(<grates_isoweek> and
<grates_epiweek> respectively) and associated
functions. Internally these are similar to the corresponding
<grates_yearweek> objects but with a marginally more
efficient implementation.
is.numeric() methods for grates objects previously
returned FALSE. Calls to these methods now dispatch to the default
implementation based on the underlying type and should now return
TRUE.seq() methods now implemented for all grates
objects.Conversion functions now preserve names.
Bug fixes for cast functions operating on objects of the same class but with different attributes.
This is a breaking release that changes the underlying implementations of the different grate constructors and associated scales for ggplot2. There has also been some renaming of function arguments to bring greater consistency across packages.
We now make more use of the high level API introduced by the clock package for working with R’s date and date-time types.
scale_x_period()
Need mirroring services?
Contact our team at info@vpspulse.com.
Mirror powered by VPSpulse
Infrastructure sponsored by VPSPulse & Secure Payments by ArionPay.