Merck / Merck/pkglite

Consider exporting `read_pkglite()`

Open
#33 2 comments 0 reactions 1 assignee View on GitHub

@nanxstats is already working on this.

Since Mar 24, 2022.

enhancement
Dominant language
R
Stars
31
Forks
4
PR merge metrics
No merged PRs in 30d

Description

It feels like it would generate more benefits than harms if we make read_pkglite() an exported function, because people might need to parse pkglite.txt directly sometimes. This would avoid the use of :::.

What do you think? @elong0527

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.