Hello,
I would like to ask whether you would consider adding support for Newtonsoft.Json as an alternative to the built-in System.Text.Json.
In some scenarios, especially when integrating elFinder.NetCore into existing projects that already rely heavily on Newtonsoft.Json (e.g., for custom converters or specific serialization behaviors), having optional support for Newtonsoft.Json would greatly simplify integration and reduce the need for workarounds.
Is this something you would be open to, either as a configuration option or as an extension point that developers could plug into?
Hello,
I would like to ask whether you would consider adding support for Newtonsoft.Json as an alternative to the built-in System.Text.Json.
In some scenarios, especially when integrating elFinder.NetCore into existing projects that already rely heavily on Newtonsoft.Json (e.g., for custom converters or specific serialization behaviors), having optional support for Newtonsoft.Json would greatly simplify integration and reduce the need for workarounds.
Is this something you would be open to, either as a configuration option or as an extension point that developers could plug into?