Skip to content

Can timechange be in Imports, not Depends? #1090

@DavisVaughan

Description

@DavisVaughan

I don't think there is any reason it should be in Depends, right? It forces lubridate to show this message when it is loaded

library(lubridate, warn.conflicts = FALSE)
#> Loading required package: timechange

We generally prefer putting packages in Imports unless there is a really compelling reason not to

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions