Previously we created custom_parse because of limitation of return type of a custom_func must be string. Since we revamped custom_func type system because of javascript introduction, seems like there is no reason for custom_parse to exist anymore. custom_parse is simply just another custom_func with transformctx and idr.Node two arguments and an arbitrary interface{} return type.
Previously we created
custom_parsebecause of limitation of return type of acustom_funcmust be string. Since we revampedcustom_functype system because ofjavascriptintroduction, seems like there is no reason forcustom_parseto exist anymore.custom_parseis simply just anothercustom_funcwithtransformctxandidr.Nodetwo arguments and an arbitraryinterface{}return type.Should we just deprecate and retire
custom_parse?