Added StringComparer property to TemplateContext

[gumbarros]

This PR allows case insensitivity at templates, making more easy to non-programmers to use variables and functions.

[hishamco]

@gumbarros check my last commit

[gumbarros]

@gumbarros check my last commit

LGTM

[hishamco]

@sebastienros anything else to add to this?

[hishamco]

Thanks for a quick fix :)

[gumbarros]

Any plans to merge this 👀?

[gumbarros]

I'm going to be out for 20 days next week and won't be able to make any changes for this PR. I would also like to use this feature this week if possible.

[hishamco]

@sebastienros any feedback on this or shall I merge?

[sebastienros]

This is too intrusive (in the ctor). Can this StringComparer be yet another property of the options/context classes, be inherited like the other properties?

And the new property should be named ModelNamesComparer? The default value should be Ordinal obviously.

[sebastienros]

@gumbarros

if you can't do the changes @hishamco or myself should be able to do it.

[hishamco]

To be honest it was as it's seen in b99e0f5

If you like how it was I will revert the latest changes considering the name that you suggested

[sebastienros]

To be honest it was as it's seen in b99e0f5

Did I actually ask the opposite, or was it done on your own thoughts?

[hishamco]

It added as property at the beginning but I saw the property appears twice in different places that's why I suggested to pass the values through constructor

[sebastienros]

In you case that's what you mean, it's pretty common to see the properties duplicated and cloned from TemplateOptions and TemplateContext. But this is done this way for anything that can alter the behavior or the rendering, to have defaults or options to share across template content instances without having to set it each time.

[hishamco]

I see if the linked commit is fine for you I will revert the latest changes then merge unless you need to add something else

[gumbarros]

Hi guys, any news on merging this 👀?

[sebastienros]

Updated it. Should be simpler, and it helped me realize that this property can't be changed dynamically as it is used by an inner collection.

In Fluid 3.0 we might want to use the same comparer for both internal properties and model properties. (note for myself)

[nguyenngocanhpro]

When will this PR be released? I've been waiting for so long.
And I think the GetValueAsync function from FluidValue should be updated in the same way as this case

[sebastienros]

@nguyenngocanhpro do you want to submit a PR for GetValueAsync? I can ship it right after that.