Repository navigation
[Proposal] Provide an option for enabling the forced debug mode #4894
Description
Is your feature request related to a problem? Please describe.
When debugging a single Dart file and setting the cwd to the root of another Flutter project, the debug mode switches to Flutter.
Describe the solution you'd like
Provide a forced debug mode option that uses the user-provided value when available, without performing automatic checks if the value has been set by the user.
Describe alternatives you've considered
Downgrade to v3.76.1
Activity
[-][fearture] Provide an option for enabling the forced debug mode[/-][+][Proposal] Provide an option for enabling the forced debug mode[/+]DanTup commentedon Dec 13, 2023
Can you provide more details about the setup (for example the
launch.configyou're using)?I think your problem might be solved by having your CLI script inside the
bin/ortool/folder, since those folders are always considered Dart scripts even when in Flutter projects.akemimadoka commentedon Dec 13, 2023
The script is placed in the
bin/directoryDanTup commentedon Dec 13, 2023
@akemimadoka can you provide an example I can use to reproduce this? I would've expected it to be broken in 3.76 and fixed in 3.78 by 7e95aeb but it sounds like you're already on 3.78?
akemimadoka commentedon Dec 13, 2023
In my case, it works fine with version 3.76 but the aforementioned issue arises with version 3.78.
DanTup commentedon Dec 13, 2023
There's a related issue at #4867 with an example that failed because
cwdwas not set, but when settingcwdit worked.Can you provide an example so I can reproduce your issue?
akemimadoka commentedon Dec 13, 2023
In my case, when I set the cwd to the root directory of the Flutter project, it will be debugged as a Flutter project.
DanTup commentedon Dec 13, 2023
Oh, I see - I thought your cwd was the same as the project containing the script. This is actually the case I imagined in the comment at #4867 (comment)
I'll close this as a dupe of #4867 (comment) and we'll tackle it there.