Request for funding: XDebug support for Flow and Neos

Hey Kay,

Unfortunately the badges have to be generated manually. I will send you yours by e-mail! Sorry for the delay!

Ok, cool - and thank you.

Derick started working on the implementation of our requested feature and will publish a report each month about the progress of his work.

You find the first of those reports on his website:
https://xdebug.org/funding/001-native-path-mapping/updates/2024-08-05

4 Likes

Derick published his second report regarding this project:
https://xdebug.org/funding/001-native-path-mapping/updates/2024-09-02

5 Likes

Derick published another report regarding this new feature:
https://xdebug.org/funding/001-native-path-mapping/updates/2024-11-01

6 Likes

Do you know an estimated/ plan when this should
be ready for production? Thanks and also big kudos to Derick :pray:

3 Likes

The latest update by Derick: Xdebug - November and December: Relative and Reverse Mappings

But no ETA, so far…

1 Like

Derick has posted an update 2025-05-13 January through May: Finishing the Initial Preview and the code is available in xdebug/xdebug and his personal fork derickr/xdebug.

I’m wondering myself. Has anyone tested the current development version in Flow so far? And are there plans to implement “Native Path Mapping” in Flow? I couldn’t find an issue or pull request on GitHub so far?

Just tested the code. It works on my machine :wink:

As this discussion here is about founding, I opened an issue on GitHub (FEATURE: Support Xdebug Native Path Mapping · Issue #3480 · neos/flow-development-collection · GitHub) to share and discuss implementation in Flow.

7 Likes

Awesome, thanks for testing and creating the issue!

Dereks Teaser Video made me wonder: Would it be possible to debug Fusion code even? :exploding_head: