Thanks Tomasz!

Initial thoughts -

• We'd need to add some tests for this
• Should we consider StringSplitOptions.RemoveEmptyEntries or similar?
• Is ; the best separator, vs. e.g. , or |, etc.?
  • ';' can be hard to grapple with in shells (e.g. where it might be a command separator)
  • using , might lead us towards supporting CSV as the value format, down the track, which has reasonably well-known escaping mechanisms
  • is there any precedent in related projects we should consider?
• The codebase doesn't use explicit private or internal
• Should we be supporting any T[] type here by recursively converting the values?
• Or, should this be one of the ExtendedTypeConversions?

I need this fix for company project I am working on. Lets see what I can change.

Any thoughts on:

• Should we be supporting any T[] type here by recursively converting the values?

Would seem to make this a more well-rounded addition.

Hi @stochmal - still interested in pushing this forward?

yes need this fix as it's broken in .NET Framework (works fine in .NET Core)

Any thoughts on:

• Should we be supporting any T[] type here by recursively converting the values?

Would seem to make this a more well-rounded addition.

tags are set in config file so it's always string to string[] conversion so don't see any use case for other array type

Any thoughts on:

• Should we be supporting any T[] type here by recursively converting the values?

Would seem to make this a more well-rounded addition.

tags are set in config file so it's always string to string[] conversion so don't see any use case for other array type

this entry in App.config is crashing Serilog

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <appSettings>
    <add key="serilog:write-to:DatadogLogs.tags" value="name:ZA2-FUNDSTI1,client:IRESS,owner:Trading,key:trading-production-za,application:FundsTradingInterface" />
  </appSettings>
</configuration>

tags are set in config file so it's always string to string[] conversion so don't see any use case for other array type

Configuration method args can be any type; if a sink takes int batchSize then value="2" will be converted today. If a method takes int[] then a value like "2,3,4" should probably work, if we're aiming for consistency.

Awesome, thanks @stochmal ! Looks good to me, too - should have this in today 👍

Nice, Thanks for your help. When will there be official release that contains that fix?

I've just opened #1614 to track the next stable release; I'll add more details there as we figure out the schedule 👍