Support file_header_template
See original GitHub issueIt seems to have problems with multi-line headers.
When you have something like:
file_header_template = this\nspans\nmultiple\nlines
the warning will be that it expects it to be all in one line.
Issue Analytics
- State:
- Created 7 months ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Project.swift
fileHeaderTemplate, Lets you define custom file header template macro for built-in ... deploymentTarget, The minimum iOS version your product will support.
Read more >Added FileHeader support with @@ syntax #762
I added support for specifying file specific headers with @@ prefix (#737 ). The file headers are processed based on the position of...
Read more >SearchReportJob.FileHeader Property
The name of the file (without path information). For PDF and HTML files, this will be the Title. %%Location%%. The location of the...
Read more >FileHeader - Packages
Powerful template with Jinja2. Custom templates supported. Rich languages supported. Support both Sublime Text 2 and Sublime Text 3. Installation. Package ...
Read more >vscode-fileheader
Extension for Visual Studio Code - insert header comment,and automatically update the time.
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
@RedX2501 JSON already interprets
\n
as a line feed character, so only the code that handles the .editorconfig setting needs to handle escape sequences.@sharwell I’ve had a quick look at the code and I didn’t find also any handling for the string that comes from the JSON. Is it safe to assume that it’s because the JSON deserializer is actually handing the line wrapping?
If that’s the case would it be enough at that line to handle the wrapping for the value coming from the editorconfig or do I need to investigate more?