We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi, I wonder if it would be possible to implement the desc$validate() method.
desc$validate()
I see that when you print a malformed description, it can show as red, but I don't understand the mechanism of how to use that generally.
I wonder if it would be possible to use the check_field() implementation, so that something like this could work out of the box.
check_field()
desc$validate("Imports") #> TRUE / FALSE or error?
It could therefore be used elsewhere like in pak or usethis to warn for malformed description.
I used usethis::use_tidy_description() with this as Imports
usethis::use_tidy_description()
Imports: commonmark cli, dplyr
And no warning occured. The warning only occured as a pak cryptic error on gh actions, and I was not able to debug myself.
Cf : r-lib/pak#632
I would be happy to open a PR with some guidance.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi, I wonder if it would be possible to implement the
desc$validate()
method.I see that when you print a malformed description, it can show as red, but I don't understand the mechanism of how to use that generally.
I wonder if it would be possible to use the
check_field()
implementation, so that something like this could work out of the box.It could therefore be used elsewhere like in pak or usethis to warn for malformed description.
I used
usethis::use_tidy_description()
with this as ImportsAnd no warning occured. The warning only occured as a pak cryptic error on gh actions, and I was not able to debug myself.
Cf : r-lib/pak#632
I would be happy to open a PR with some guidance.
The text was updated successfully, but these errors were encountered: