-
-
Notifications
You must be signed in to change notification settings - Fork 13
fix(sections): keep fenced code blocks in a description intact #709
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
fe87da0
fix(sections): keep fenced code blocks in a description intact
claude 13fa01d
fix(sections): read a line opening with inline code as prose
claude 7ca78eb
fix(sections): find description fences by parsing the description
claude b2a61c6
fix(sections): tell indented code from fenced blocks in descriptions
claude File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,83 @@ | ||
| /** | ||
| * Covers how an action.yml description becomes the description section. | ||
| */ | ||
| import { describe, expect, it } from 'vite-plus/test'; | ||
|
|
||
| import { descriptionMarkdown } from '../src/sections/update-description.js'; | ||
|
|
||
| describe('descriptionMarkdown', () => { | ||
| it('squashes prose and turns blank lines into breaks', () => { | ||
| expect(descriptionMarkdown(' One line \nnext\n\nNew paragraph ')).toBe( | ||
| 'One line\nnext<br />New paragraph', | ||
| ); | ||
| }); | ||
|
|
||
| it('reads CRLF line endings as LF', () => { | ||
| expect(descriptionMarkdown('A\r\n\r\nB')).toBe('A<br />B'); | ||
| }); | ||
|
|
||
| // #705: a fence keeps its own lines, set apart from the prose by blank lines. | ||
| it('keeps a fenced code block verbatim on lines of its own', () => { | ||
| const description = [ | ||
| 'Does things.', | ||
| '', | ||
| '```yaml', | ||
| 'uses: x', | ||
| '', | ||
| ' with: y', | ||
| '```', | ||
| '', | ||
| 'After it.', | ||
| ].join('\n'); | ||
|
|
||
| expect(descriptionMarkdown(description)).toBe( | ||
| ['Does things.', '', '```yaml', 'uses: x', '', ' with: y', '```', '', 'After it.'].join( | ||
| '\n', | ||
| ), | ||
| ); | ||
| }); | ||
|
|
||
| it('closes a fence only on a fence of the same character and at least its length', () => { | ||
| const description = ['````', '```', '~~~~', '````', 'after'].join('\n'); | ||
|
|
||
| expect(descriptionMarkdown(description)).toBe( | ||
| ['````', '```', '~~~~', '````', '', 'after'].join('\n'), | ||
| ); | ||
| }); | ||
|
|
||
| it('keeps an unclosed fence to the end, as it renders', () => { | ||
| expect(descriptionMarkdown('Intro\n\n~~~\nopen only')).toBe('Intro\n\n~~~\nopen only'); | ||
| }); | ||
|
|
||
| // A backtick fence's info string cannot hold a backtick, so this line is an | ||
| // inline code span. | ||
| it('reads a line opening with an inline code span as prose', () => { | ||
| expect(descriptionMarkdown('```code``` is prose\n\nnext para')).toBe( | ||
| '```code``` is prose<br />next para', | ||
| ); | ||
| }); | ||
|
|
||
| it('keeps a fenced code block inside a list item verbatim', () => { | ||
| const description = ['- Run:', '', ' ```yaml', ' uses: x', '', ' ```', '- Done'].join( | ||
| '\n', | ||
| ); | ||
|
|
||
| expect(descriptionMarkdown(description)).toBe( | ||
| ['- Run:', '', ' ```yaml', ' uses: x', '', ' ```', '', '- Done'].join('\n'), | ||
| ); | ||
| }); | ||
|
|
||
| it('squashes an indented code block as prose, as before', () => { | ||
| expect(descriptionMarkdown('Intro\n\n indented line')).toBe('Intro<br /> indented line'); | ||
| }); | ||
|
|
||
| it('squashes an indented code block whose first line is backticks as prose', () => { | ||
| expect(descriptionMarkdown('Intro\n\n ```not a fence\n x')).toBe( | ||
| 'Intro<br /> ```not a fence\n x', | ||
| ); | ||
| }); | ||
|
|
||
| it('leaves backticks that do not start a line as prose', () => { | ||
| expect(descriptionMarkdown('Use ``` inline')).toBe('Use ``` inline'); | ||
| }); | ||
| }); |
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.