| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
| textToLog = textToLog.Replace('\u0000', '\u2400'); | ||
| #if UNIX | ||
| if (Platform.IsLinux) | ||
| { |
There was a problem hiding this comment.
This check is not needed.
Sorry, something went wrong.
There was a problem hiding this comment.
Why? This is only an issues for SysLog, not OsLog on macOS
Sorry, something went wrong.
There was a problem hiding this comment.
Got it. Closed
Sorry, something went wrong.
There was a problem hiding this comment.
In the case it would be good to have the protection comment in the code.
Sorry, something went wrong.
There was a problem hiding this comment.
I can repeat the comment if you want
Sorry, something went wrong.
There was a problem hiding this comment.
It is explained on line 1584
Sorry, something went wrong.
|
Talked with Travis Plunk (@TravisEz13) about the concern of creating 3 large strings for Linux when the script itself is large. |
Sorry, something went wrong.
| [string] $powershell = Join-Path -Path $PSHome -ChildPath 'pwsh' | ||
| $scriptBlockCreatedRegExTemplate = @" | ||
| Creating Scriptblock text \(1 of 1\):#012{0}(`u{23CE}|\?|#012)*ScriptBlock ID: [0-9a-z\-]*#012Path:.* | ||
| Creating Scriptblock text \(1 of 1\):#012{0}(⏎|#012)*ScriptBlock ID: [0-9a-z\-]*#012Path:.* |
There was a problem hiding this comment.
Why do we need this? `u{23CE} looks more clear for me.
Sorry, something went wrong.
There was a problem hiding this comment.
The tests fail if we use the escape sequence.
Sorry, something went wrong.
There was a problem hiding this comment.
I tried to copy and paster the code in console and lost the char. Also the tests become unreadable. I wonder why doesn't the Unicode syntax sugar work?
Sorry, something went wrong.
There was a problem hiding this comment.
Ilya (@iSazonov) that's going to vary by the font you use. I worked with Rob Holt (@rjmholt) to come up with this solution. The previous solution that was working, was actually just looking for a ? which is less specific.
Sorry, something went wrong.
There was a problem hiding this comment.
I remember that we had Unicode chars in files and it was a headache - editors silently break them. After that we made a conclusion to keep all files in ASCII.
Sorry, something went wrong.
|
🎉v7.0.0-preview.5 has been released which incorporates this pull request.:tada: Handy links: |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PR Summary
Replace CR and new line with a 0x23CE character
PR Context
Trying to document how to use logging with Azure Log Analytics and RSyslog converting these to #012 and #013
PR Checklist