[IMP] Support debugging modules from nested doodba subprojects in VSCode #525
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
josep-tecnativa
force-pushed
the
imp-add-debugger-to-special-repos
branch
from
1141d65 to
8eccdb6
Compare
josep-tecnativa
changed the title
josep-tecnativa
force-pushed
the
imp-add-debugger-to-special-repos
branch
13 times, most recently
from
dd8dd1c to
1069b09
Compare
josep-tecnativa
force-pushed
the
imp-add-debugger-to-special-repos
branch
from
1069b09 to
bc80deb
Compare
CarlosRoca13
approved these changes
Mar 5, 2025
pedrobaeza
approved these changes
Mar 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the workspace generation to detect doodba subprojects and add their modules from odoo/custom/src/private to the VSCode debug path. If a .copier-answers.yml indicates a doodba-copier subproject, we scan for modules there and configure them automatically for debugging. Otherwise, the script follows the existing one-level scan.