Namespaces in Imports field not imported from about areal HOT 4 CLOSED

Thanks @edzer - we want to make sure lwgeom is installed because we use sf::st_area in the package. So while we don't import anything directly, it is a necessary dependency that isn't installed automatically by sf. At least that is how I am thinking about it - am I off base there?

With tibble - my understanding is that if a package prints an object as a tibble but the user does not have tibble installed, there are issues with printing the object. So therefore safter to require tibble as a dependency? Again, would love your perspective here.

Thanks for the feedback!

from areal.

st_area is in sf, and sf only class lwgeom stuff if the data are in geodetic coordinates, which is often not the case, so you don't actually need it, and sf will tell you when you need it. tibble is a dependency of dplyr, so comes automatically when you import dplyr.

If CRAN has no problems with what you do, then I also don't.

from areal.

We put it in when we were testing the package and were prompted to install lwgeom by sf. I'll revisit whether it is necessary, though. CRAN had no problems.

from areal.

have removed lwgeom (shouldn't be needed since projected coords required by functions) and tibble (which should be installed along with dplyr)

from areal.