You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While maybe a little confusing, I don't think this is a bug. With classed objects, like hms, our general goal is to make sure that we retain only the attributes known and managed by the class. In the case of hms, that's the class attribute and the units attribute. It is an impossible problem to ensure that the class is kept in a "correct" state if we always copy over all attributes, including "unknown" ones not managed by the class.
We don't make any promises about other attributes and you really can't expect them to be kept.
With "bare" vectors that don't have any classes, we've made an exception to try and drag along attributes that might be attached, but this is mostly a historical thing and not something we encourage.
In general if you want to retain extra attributes you should create your own S3 class that "knows" about that attribute and can restore them (like with a vctrs::vec_restore() method)
In the data frame returned by
arrange()
, the attribute ofhms
class variable disappears, though the attributes of other variables are preserved.The text was updated successfully, but these errors were encountered: