Here is what to include in your request to make sure we implement a solution as quickly as possible.
1. Description
I'd like to propose a way to re-configure the sliding cache used by the ConstantExpressionHelper.
2. Exception
N/A
3. Fiddle or Project
N/A
4. Any further technical details
As it currently stands (to my understanding), the ConstantExpressionHelper is constructed once via ConstantExpressionHelperFactory.
By backtracking on ConstantExpressionHelperFactory.GetInstance() calls, it looks like the only way to configure the sliding cache is via the first usage of extended methods like Where() and others that can take in a ParsingConfig parameter.
I feel like this could be handled better where the sliding cache is configured via some static method as the class itself is virtually a singleton.
This would then make it easier for consumer applications to easily dictate a Time-To-Live setting (for example) that works best for them.
I'm happy to provide a PR if that helps.
Here is what to include in your request to make sure we implement a solution as quickly as possible.
1. Description
I'd like to propose a way to re-configure the sliding cache used by the ConstantExpressionHelper.
2. Exception
N/A
3. Fiddle or Project
N/A
4. Any further technical details
As it currently stands (to my understanding), the ConstantExpressionHelper is constructed once via ConstantExpressionHelperFactory.
By backtracking on
ConstantExpressionHelperFactory.GetInstance()calls, it looks like the only way to configure the sliding cache is via the first usage of extended methods likeWhere()and others that can take in aParsingConfigparameter.I feel like this could be handled better where the sliding cache is configured via some
staticmethod as the class itself is virtually a singleton.This would then make it easier for consumer applications to easily dictate a Time-To-Live setting (for example) that works best for them.
I'm happy to provide a PR if that helps.