Skip to content
New issue

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

allow reporter = "silent" for specific tar_targets #1293

Closed
stemangiola opened this issue Jun 5, 2024 · 1 comment
Closed

allow reporter = "silent" for specific tar_targets #1293

stemangiola opened this issue Jun 5, 2024 · 1 comment
Assignees

Comments

@stemangiola
Copy link

Prework

  • [ x] I understand and agree to help guide.
  • [ x] I understand and agree to contributing guide.
  • [ x] New features take time and effort to create, and they take even more effort to maintain. So if the purpose of the feature is to resolve a struggle you are encountering personally, please consider first posting a "trouble" or "other" issue so we can discuss your use case and search for existing solutions first.

Proposal

We are using Targets to make scalable APIs (HPCell). This pipeline is decided by the user, and we build a custom pipeline from the API calls, of this sort.

step_1() > step_2() |> step_3() |> ...

or

step_1() > step_3() |> ...

Sometime, targets are not defined, and it simplifies the implementation to create dummy targets (=NULL) anyway. However the messaging of a target (that should not exist) being build is confusing for the user.

it would be beneficial to have

tar_target(normalisation, NULL, reporter = "silent")

so that such a target gets built but in the background.

Thanks.

@wlandau
Copy link
Collaborator

wlandau commented Jun 5, 2024

I don't have plans to redesign the reporter infrastructure to make this work there, but as long as you are developing a custom API, you could make use of tar_progress() and other functions in https://docs.ropensci.org/targets/reference/index.html#progress and filter out the NULL targets.

@wlandau wlandau closed this as not planned Won't fix, can't repro, duplicate, stale Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants