Closed yihui closed 7 years ago
I have updated the docs and the release notes: That flag is removed as it has no practical appliance anymore; we use the archetype files as you write them -- and all front matter formats are supported.
The conversion to YAML was actually useful to me because YAML is best supported in my world (R language). I will need to work much harder to support TOML. Is it hard to keep this argument? Thanks!
Is it hard to keep this argument? Thanks!
It will not happen. If you want YAML: Create your archetype file(s) with YAML format. Easy.
Yeah I know that. The problem is this: a theme author may have provided a TOML-based (or JSON) archetype file, but the user does not have one. In this case, hugo new
will generate the metadata in TOML, and I wish it could convert it to YAML instead.
If hugo convert toYAML
can work on a single file instead of a whole directory, that will help, too.
I can certainly ask users to create a YAML-based archetype file, but it will be better if fewer instructions are needed.
If hugo convert toYAML can work on a single file instead of a whole directory, that will help, too.
That we can do, but you would have to create an issue for that.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
It used to work before 0.23, and the doc says
-f
is supported: http://gohugo.io/commands/hugo_new/