fix: don't try to encode dap_open_command in JSON

[judemille]

dap_open_command is a function, and Neovim gets very angry when asked
to encode a function in JSON. I don't know if it silently allowed this
before or what, but it's causing issues for me.

This just temporarily stores it, clears it in the project config while
encoding, and then puts it back. Simple enough.

[Shatur]

dap_open_command is a function, and Neovim gets very angry when asked

How can I reproduce it?

[judemille]

How can I reproduce it?

Open a new project. Try to change a project setting (e.g. CMake args). This will cause the error in my environment.

Specificities: Up to date Arch Linux, LunarVim.

[Shatur]

Can't reproduce also on Arch. What Neovim version are you using?

[judemille]

NVIM v0.9.5
Build type: Release
LuaJIT 2.1.1702233742

[Shatur]

Same... I guess it depends on the dap config?
There is a recent issue about it, maybe we should reconsider how dap should be integrated?
#22

[judemille]

I use the default function for DAP integration in this plugin, so I don't know why anything special would occur. Regardless, we shouldn't be encoding a function in JSON.

As for reconsidering DAP integration: That may well be a good idea.

[judemille]

In the meantime, can this be merged?