Post #1689005
2026-04-02 13:10 UTC
@defuneste @milesmcbain @drdcarpenter @mschmidty
Great point. For my use case it’s just a small set of project‑specific inputs that I like keeping out of the script, but I totally get how YAML can sprawl as things grow.
For the list method how do you normally structure that in practice? Do you keep the list inside the main script, or pop it in a separate config.R (or similar) and source it?
Replies (1)
-
@defuneste@fosstodon.org 2026-04-02 13:17
@lwpembleton @milesmcbain @drdcarpenter @mschmidty I did all of the below: - the list like a function() (packaged or not) - the list like data (attached or not) - the list like object in a new env with "method" to update it - source it - "target" it - yaml (I confess and repent) I think I like the option of creating a specific env, with functions to update it (yeah I know R6 ...). Similar to "the" in R package book. It depends how easy you want to update the$list :)