Zev Spitz

The library doesn't support this behavior, because the expression tree doesn't reflect it. What should be the output of the following code? ```csharp int IdProjeto = 3; Expression exp =...

You can create a custom renderer and register it as described [here](https://github.com/zspitz/ExpressionTreeToString/wiki/Extensibility-and-plugin-mechanism). In your case I would suggest writing a class that inherits from [**DynamicLinqWriterVisitor**](https://github.com/zspitz/ExpressionTreeToString/blob/master/Library/DynamicLinqWriterVisitor.cs), providing an overriding implementation of...

It's certainly possible. Could you better clarify what's your use case? Also, specifically WRT your example, my initial thinking would be as follows: ```csharp Expression ex = (value, index, values)...

@StefH Any further thoughts on this?

An initial first step is #36. Once that works, it might be nice to have a plugin system -- e.g., when the main DLL is loaded, load plugin DLLs --...

(Putting this here as the first extensibility-related issue.) We have to distinguish between writers (Func, the boolean indicates whether to return path spans) and writer-visitors (WriterBase and derived classes). There...

RE: plugin mechanism: there could be a public method on Renderers `Load`, taking a relative or absolute path, and loading the referenced path. Within the loaded DLL, search for a...

I will try to add this at some point, but I can't provide a precise timeline. Why is the following interface necessary? ```csharp public interface IVisualizerConfigurationProvider { Func GetTypeName {...

On further consideration, it may not be necessary to pass an option to the `RenderLiteral` function. All that is needed is to expose two additional extension points: `WriteTypename` and `WriteLiteral`,...

We could also test that the generated expression tree looks the same as the original, via one of the renderings.