You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @TonyValenti, regarding string.ToInterpolatedString(), I'm removing this in v9 because 1) string it very overloaded already and 2) creating the InterpolatedString ahead of time is a pretty advanced feature which is better served by using the InterpolatedStringResolver.
I see the Resolver as the preferred way to interact with the library now as it is settings aware and all the methods are provided with the settings in context. In contrast, using the string extensions either means using the global settings or passing in the settings objects for every expansion.
Version 9 is out today.
The text was updated successfully, but these errors were encountered:
Hi @TonyValenti, regarding
string.ToInterpolatedString()
, I'm removing this in v9 because 1)string
it very overloaded already and 2) creating theInterpolatedString
ahead of time is a pretty advanced feature which is better served by using theInterpolatedStringResolver
.I see the Resolver as the preferred way to interact with the library now as it is settings aware and all the methods are provided with the settings in context. In contrast, using the string extensions either means using the global settings or passing in the settings objects for every expansion.
Version 9 is out today.
The text was updated successfully, but these errors were encountered: