Prettify markdown RPC message rendering with proper JSON indentation#168
Merged
Prettify markdown RPC message rendering with proper JSON indentation#168
Conversation
- Remove JSON compression logic to enable proper pretty printing with 2-space indentation - Add logic to hide JSON blocks when only params:null or empty object remains after field removal - Update formatJSONWithoutFields to return isEmpty boolean - Add new test cases for params:null and empty object scenarios - All tests passing Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Prettify markdown rendering for RPC messages
Prettify markdown RPC message rendering with proper JSON indentation
Jan 11, 2026
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
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.
RPC messages in markdown logs were using compressed single-line JSON format and showing empty payloads. This makes logs harder to read when debugging message flows.
Changes
JSON formatting (
internal/logger/rpc_logger.go){ ... }json.MarshalIndentwith 2-space indentation for proper pretty printingEmpty payload handling
isEffectivelyEmpty()to detect when onlyparams: nullor empty objects remain after field removalformatJSONWithoutFields()to returnisEmptyboolean alongside formatted outputformatRPCMessageMarkdown()to omit JSON code blocks when payload is effectively emptyBefore:
After:
With content - Before:
With content - After:
Test updates
TestFormatJSONWithoutFieldsfor new 3-value return signatureparams: nulland empty object edge casesOriginal prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.