Kurita Takashi

Thank you for your comment. I didn't know `DebugKit` calls `__debugInfo()`. Then it would be an idea. But first, let me try to fix this [walker](https://github.com/cakephp/debug_kit/blob/0ba4f3639c2f2637b7b4575dd4fae541d83ff3fa/src/Panel/VariablesPanel.php#L101-L152). If it ensures that...

It was not so easy :disappointed: At first I was planning to replace closures with string '(closure)' recursively. But it would break objects in view variables, or runs into infinite...

If we don't need to use `serialize()`, then I think the built-in `var_export()` may be a good function. It can stop when recursion detected.

Hmm. It seems to be harder than I thought. Indeed, using `var_export()` doesn't make sense as we would get `Call to undefined method Closure::__set_state()` instead of `Serialization of 'Closure' is...

Oh sorry, I forgot about this issue. Now I am thinking fixing Form::__debugInfo() would be safe, as I am not sure if using Debugger::exportVar() doesn't cause another issues [like this](https://github.com/cakephp/cakephp/issues/11507).

I think the current implementation will drop not only triggers but also indexes. We would need to follow the way shown in the official documentation: https://sqlite.org/lang_altertable.html#otheralter And, I thought we...