File edit differences to the Server Activity Log - #105
Merged
Merged
Conversation
Owner
|
very well done, will impliment into v1.1.5 |
macery12
added a commit
that referenced
this pull request
Feb 3, 2026
File edit differences to the Server Activity Log
macery12
added a commit
that referenced
this pull request
Feb 3, 2026
File edit differences to the Server Activity Log
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 pull request improves the Server Activity Log by displaying detailed, review-friendly differences whenever a server owner or subuser edits a text-based file through the web editor. Each activity entry now records the exact file path and presents a structured summary of added and removed lines, with an expandable pull request style view of the changes.
Key Changes
Introduced a dedicated file write endpoint with change tracking ([/files/write-with-diff] to capture sufficient context for calculating differences between the original and updated content.
Implemented server-side calculation of file content differences for text files without relying on development-only dependencies, ensuring production compatibility.
Updated the client file editor save flow to send both the original content and the updated content, enabling accurate calculation of differences.
Enhanced the Activity Log interface to display line change statistics and a collapsible, hunk-based view of the differences for [server:file.write] events.
Added performance safeguards for large files by recording only summary information when detailed calculation is not practical.
Compatibility Notes
The existing [/files/write] endpoint remains unchanged and continues to be used as a fallback when original content is not provided.
Change tracking is currently intended for edits performed through the web editor; other write paths continue to operate normally without generating detailed differences.
Please review and make changes. I would love for this idea to be fully integrated.