Delete break points conditions historic
已回答
Is it possible to delete the old, outdated, incomprehensible, cumbersome and potentially bugged break point conditions ?
请先登录再写评论。
Hi Brice,
Breakpoints are stored in the file called workspace.xml located in the project configuration folder (.idea) located in the project root. The format is as follows:
You can remove any or all lines from it that look like
<condition expression="..." language="JAVA" />Hello, sorry for the delay.
Thank you for the answer, i have effectively a
XDebuggerManagernode in this file, but no trace ofcondition expressionin the whole file, yet when i create a breakpoint the condition popup contains about fifty conditions.A drop-down list is not necessarily the best widget for this feature, a condition is rapidly disposable, but not systematically, to be able to modify the rank of a condition independently of its seniority, or thus delete it, manually or automatically like the cookies in a browser, could be useful.
Hi Brice,
Sorry, that was a misunderstanding on my part. Condition history should be cleared when you perform the File | Invalidate Caches operation with the first three options checked, but I understand that it may not be the best solution.
I created https://youtrack.jetbrains.com/issue/IJPL-186126 to make it possible to clear the history from the UI directly. You are welcome to upvote it and leave additional comments for our developers. Thank you!
Hello, it seems that it doesn't work either, or i don't have understood something, but based on your first answer, inside the config folder there is a workspace repertory where the previous workspaces are stored with UID names, and in the last xml file all the conditions can be found under the <expressions id="breakpointCondition"> node, and if i delete it, it works, clearly not convenient.
Thank you for the ticket.
Hi Brice,
We agree — manually deleting the breakpoint condition history isn’t ideal. That’s why we’ve logged this internally as IJPL-186126.
We encourage you to upvote or comment on the issue to help prioritize the feature.