Add support for reactive stream debugging

[gayanper]

Add support for debugging reactive streams where we can trace different steps and exactly their definition locations on the source code.

Example in IJ

This will benefit debugging java streams as well.

[nickzhums]

Hi Gayan Perera (@gayanper), thanks for opening this issue. We will definitely look into this one. Meanwhile, feel free to provide as much as info as you need

[jimisola]

Any updates?

[github-actions]

Hi Gayan Perera (@gayanper), I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

Suggested Approach

• Use Step Into Target: The Java Debug extension (vscode-java-debug) introduced the “Step Into Target” feature (PR #434), now available in the pre-release and in stable 0.46.0.
  • This lets you step directly into lambda expressions or operator implementations in your reactive pipelines.
  • Install the latest version or the pre-release from the extension’s release notes.

Current Status

• A dedicated reactive-streams debugging UI (similar to IntelliJ’s Reactor Debug Mode) is not yet implemented.
• Feel free to open or upvote a feature request on the Java Debugger repo to track this enhancement.

References

• Support Step Into Target (implements advanced stepping, useful for lambdas/operators)
  • Issue comment: Support Step Into Target #1192 (comment)

Other references with low confidence

• Add support for doing advance Java Search similar to Eclipse (search enhancements) – Add support for doing advance Java Search similar to Eclipse redhat-developer/vscode-java#1641
• Expose lists of tests for task.json inputs (test integration) – Expose lists of tests to be usable in inputs of task.json vscode-java-test#1405 (comment)
• Debugger to work with standalone source file (standalone debugging) – Debugger to work with standalone source file #94

The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!