-
-
Notifications
You must be signed in to change notification settings - Fork 732
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add pre-processor directive which injects Debugger.Break() #869
Comments
@mholo65 not a problem. That is why it says this:
At the very bottom, so you are good! 😄 |
@patriksvensson when are PR's due for v0.12.0? Noticed that You've postponed this to v0.13.0, but I may have time to implement this during this week. Would be a great addition to debugging.. |
@mholo65 it's a matter of how much time we have 😉 , but please submit the PR when ready and if v.12.0 isn't released we might be able to review and merge before, otherwise it'll just go in the next release. 😄 |
ping @patriksvensson @devlead So, I started looking into this, but I'd like some pointers on the design. Main problem is that Processors (Cake.Core.Scripting) doesn't currently have the possibility to modify the current line. (Should they?) I could just return true if a The above solution feels kind of ad hoc, or what's your opinion? Personally, I would like to inject inside the Processor if debug is enabled but that will mess up line numbers. |
@mholo65 I'm taking a look at this now. Will get back to you asap. |
@mholo65 I think the easiest approach for now is to add an out parameter for the LineProcessor where we can return a replacement line if the line processor returned true.
We would have to update the existing processors to set the replacement to
The replacement can never exceed one line to not mess with the line numbering. |
Thanks @patriksvensson, really appreciated! I'll try to get a PR in tomorrow! |
@patriksvensson also, in addition to this, it would be nice if
And when #876 is implemented |
@mholo65 Great suggestion. Have to think about that a little since we have plans to redesign |
Closed via #903. |
Once #858 is merged, there will be use for a pre-processor directive that injects System.Diagnostics.Debugger.Break();.
This should only be injected when debug option is used.
Sorry for not using the template, but it doesn't seem to fit for new features 😄
The text was updated successfully, but these errors were encountered: