fix(issues): interpret \n escape sequences in --description flag#162
Merged
fix(issues): interpret \n escape sequences in --description flag#162
Conversation
The --description flag passed literal \n characters through to ADF conversion, resulting in visible \\n text in Jira instead of paragraph breaks. Now interprets C-style escape sequences (\n, \t, \\) in the description string before converting to ADF, matching user expectations when using inline descriptions. Adds internal/text package with InterpretEscapes utility for reuse by other commands. Applied to both issues create and issues update.
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.
Summary
Fixes #161
internal/text.InterpretEscapes()to convert C-style escape sequences (\n,\t,\\) in CLI flag values to actual control characters--descriptionin bothjtk issues createandjtk issues update--description "First paragraph.\n\nSecond paragraph."and get proper paragraph breaks in JiraTest plan
InterpretEscapescovering all edge cases (trailing backslash, unknown escapes, already-real newlines, empty string)TestRunCreate_DescriptionEscapeSequencesverifying escaped newlines produce multiple ADF nodesgo test ./tools/jtk/...)golangci-lint run)