EditorHelpBit: Workaround crash renaming named class inheriting @tool
class
#102729
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 only addresses the symptom, not the root cause of the problem.
In the MRP of the linked issue, the parent class seems to not be found in DocData after renaming its child class, which seems weird. Force opening the docs of the parent class can work it around, so we seem to have inconsistent state.
Changed the same code in EditorHelp for good measure.
Fixes #102718.
A more proper fix would be to ensure that the parent class isn't lost from the DocData when renaming the child class. Maybe we're lacking some explicit update somewhere.
The problem might also be related to the fact that the parent class is
@tool
in the MRP, but the derived class isn't: