Open KatherineKayMRG opened 5 months ago
It's expected, sort of. yaml
sees a bare n
and it interprets that as "no", turning abb
into a logical value. When you write "n"
, you're telling the parser that you mean this to be a character value.
You'll see the same error if you call
df <- yaml_as_df(here("report/glossary.yaml"))
We could document this better, but don't know how helpful that would be in the wild. Maybe some other stuff we could do help when this happens, but I don't think there is any way to write bare n
and not have yaml turn that into FALSE
.
Ah ok, sorry I didn't make the connection between n > no > FALSE
for yaml. I'm not sure where to suggest documenting it but I guess it might not be important often?
Thanks for following up
I included the following in a glossary yaml
when trying to run
glo <- read_glossary(here("report/glossary.yaml"))
I got an errorIt was fixed with
Is this expected behaviour? Is there anything we can do? It's such an unhelpful error message