Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Discussion: list_ods_sheets vs ods_sheets #133

@chainsawriot

Description

@chainsawriot

Following up #131, I think it is better to leave this for the community to decide. The interim solution so far is to keep ods_sheets at least until v3. But what should we do for v3?

list_ods_sheets conforms to the so-called Tidy Design Principles on function names. It's a verb. All other functions (although not many) in this packages are verbs: read_ods and write_ods.

However, readxl::excel_sheets violates the Tidy Design Principles, even though readxl is part of Tidyverse. If readODS emulates readxl, we should keep ods_sheets. An additional argument is reverse dependencies: several packages use ods_sheets.

Looking beyond readxl, DBI uses dbListTables. There are also base functions such as list.files, list.dirs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions