Document `cli.default_handler` option

Open
#708 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
r
Domain
cli, documentation

Research direction

No file or test is named in the issue. Start by locating the existing documentation for cli.default_handler and the cli_message class, then inspect how the handler receives and can convert the message. Done means both the option and class are documented well enough to explain the argument and how to save the message as character data.

Written by the indexing model from the issue text.

Description

documentation feature

The existence of the cli.default_handler option is documented, and I've established that this has to be set to a function with 1 argument. Unfortunately I'm not sure how to work with this argument. It seems to be a cli_message object, which has no methods.

> str(message)
List of 4
 $ message: chr "cli message alert_warning"
 $ type   : chr "alert_warning"
 $ args   :List of 4
  ..$ text :List of 2
  .. ..$ str   : chr "<FCkNXbE-1v5FCkNXbE-1>: <FCkNXbE-1v6FCkNXbE-1>"
  .. ..$ values:<environment: 0x562267b28480> 
  .. ..- attr(*, "class")= chr "cli_glue_delay"
  ..$ id   : chr "cli-155-1"
  ..$ class: NULL
  ..$ wrap : logi FALSE
 $ pid    : int 155
 - attr(*, "class")= chr [1:2] "cli_message" "condition"
> class(message)
[1] "cli_message" "condition"`

In practice I just want to convert the message to a character vector and then save it somewhere. However this class doesn't seem to have a format() method or anything. Can we please document this class and also the cli.default_handler function?

Dominant language
R
Stars
726
Forks
94
Avg merge
3h 35m
Merged PRs (30d)
1

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.

More from r-lib/cli

All issues in r-lib/cli

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.