.Trim() ruins OutputTemplate={NewLine}

[tagcode]

UdpSink calls .Trim() which removes {NewLine} behaviour and makes it impossible to formulate the message as the user wants.

[github-actions[bot]]

Hi there and welcome to this repository!

A maintainer will be with you shortly, but first and foremost I would like to thank you for taking the time to report this issue. Quality is of the highest priority for us, and we would never release anything with known defects. We aim to do our best but unfortunately you are here because you encountered something we didn't expect. Lets see if we can figure out what went wrong and provide a remedy for it.

[FantasticFiasco]

Correct me if I’m wrong, but it only removes all leading and trailing white-space characters. Is it a trailing whitespace that is removed in your application?

[tagcode]

Yes, trailing whitespace is removed. I'm using OutputTemplate="{EventId}{NewLine}" and capturing it with netcat in a bash script. The script cannot distinguish different lines because "{NewLine}" is consumed by the sender. Similarly, OutputTemplate="{Message}{NewLine}" also sends endless blocks of texts without linefeed.

[FantasticFiasco]

I'll look into it, cant remember why I added it, bit since changing it would be a breaking change I have to investigate it further.

[tagcode]

Okay. I suppose you considered packet boundary as equivalent information to whitespace/linefeed.

I think the options here are:

• New major version line and having the breaking change there, which is considered acceptable so long the change informed in readme.
• More configuration options (not elegant).

[FantasticFiasco]

A new major version with your fix is now available on nuget.org, you've also been mentioned in the changelog.

Thank you for reporting this!

[tagcode]

👍 Tried it and it works now exactly as in OutputTemplate. I appreciate.