Bug: YAML Title does not pull from filename
See original GitHub issueDescribe the Bug
If there are any headers in the file, “YAML Title” will pull the first header for the title instead of using the filename (or even an h1 later in the file) for the YAML title field.
How to Reproduce
Steps to reproduce the behavior:
- Create a file with a header besides an h1
- Lint
- The YAML will contain
title: headername
Expected Behavior
The YAML should contain title: filename
Device
- Desktop
- Mobile
Issue Analytics
- State:
- Created 10 months ago
- Comments:9
Top Results From Across the Web
Use H1 titles (#) in the sidebar, similar to YAML title. #1011
When using title in a YAML header, in the sidebar, the filename is replaced by the ... This is not to be considered...
Read more >Have different .RMD file and output file names - Stack Overflow
I'm having troubles name my output PDF file from my "Knit with Parameters" RMD file. my YAML ...
Read more >10 YAML tips for people who hate YAML | Enable Sysadmin
Do you hate YAML? These tips might ease your pain.
Read more >Customize your pipeline - Azure Pipelines - Microsoft Learn
Open the YAML editor for your pipeline. · Add the following snippet to the end of your YAML file. YAML Copy · Select...
Read more >file_put_contents - Manual - PHP
This function is identical to calling fopen(), fwrite() and fclose() successively to write data to a file. If filename does not exist, the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Interesting. I will see if I can reproduce this when I get a chance later this week.
For future reference, it would help if the initial creation of these bugs and feature requests included the example to help avoid misunderstandings on my or other dev’s parts as the example makes it clear that you mean a non-H1 header while the words describing this scenario are a little more ambiguous.
This should be fixed on master and in the next release. Please let us know if that is not the case.