TL;DR

Update the _extract_field method in rule_engine.py to handle both 'new_string' and 'content' keys for the new_text field.

Guidance

• Identify the line of code causing the issue (line 239 in rule_engine.py) and update it to check for both 'new_string' and 'content' keys.
• Verify the fix by creating a hookify rule with event: file and field: new_text, then trigger a Write tool call to ensure the rule matches as expected.
• Test the fix with both Edit and Write tool operations to ensure compatibility.
• Review other parts of the codebase that may rely on the new_text field to ensure this change does not introduce any regressions.

Example

return tool_input.get('new_string') or tool_input.get('content', '')

This code snippet updates the _extract_field method to return the value of either 'new_string' or 'content' from the tool_input dictionary.

Notes

This fix assumes that the 'new_string' and 'content' keys are mutually exclusive in the tool_input dictionary. If this is not the case, additional logic may be needed to handle the overlap.

Recommendation

Apply the workaround by updating the _extract_field method as described, as it provides a clear and targeted solution to the issue.