`ActionContext.GetContext<string>("property")` returns json token of `{{ ValueKind: 3}}` instead of actual value.

Hi,

I’m using 3.2.0.

I have a custom action in a action trigger:

 public class PropertySetterAction : ActionBase
    {
        private readonly RuleExpressionParser _expressionParser;

        public PropertySetterAction(RuleExpressionParser expressionParser, object input)
        {
            _expressionParser = expressionParser;
        }
        public override ValueTask<object> Run(ActionContext context, RuleParameter[] ruleParameters)
        {
            
            var propertyName = context.GetContext<string>("propertyName");
            var value = context.GetContext<string>("newValue");
            
            return new ValueTask<object>(this._expressionParser.Evaluate<object>(value, ruleParameters));
        }
    }

Debugger view:

My Rules look like this:

[
  {
    "WorkflowName": "Employee Validations",
    "Rules": [
      {
        "RuleName": "If Employee Last name is unset, use first name as last name",
        "Expression": "!string.IsNullOrWhiteSpace(input1.LastName)",
        "Actions": {
          "OnFailure": {
            "Name": "PropertySetterAction",
            "Context": {
              "propertyName": "LastName",
              "newValue": "input1.FirstName"
             }
          }
        }
      }
    ]
  }
]

My expectation is that propertyName in context would be the literal LastName and the value of newValue would be evaluated to an expression.

Am I missing something or is there a defect?

[abbasc52]

@ElanHasson I digged deeper into the issue and realized that System.Text.Json does not play well with Object type and generates valuekind like object. https://josef.codes/custom-dictionary-string-object-jsonconverter-for-system-text-json/

It looks like something beyond the scope of this library, and we would recommend using Newtonsoft (or pass the json as string) till we are able to fully migrate to System.Text.Json

I will be closing this issue for now and will include this as a part of documentation

[ElanHasson]

@abbasc52, what is the work necessary to support? I can send a PR.

Any interest in supporting whatever serializer via configurable extensibility points in ReSettings?