Skip to content
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

Inline shortcode regression #6677

Closed
bep opened this issue Dec 27, 2019 · 2 comments · Fixed by #6679
Closed

Inline shortcode regression #6677

bep opened this issue Dec 27, 2019 · 2 comments · Fixed by #6679
Labels
Bug
Milestone

Comments

@bep bep added the Bug label Dec 27, 2019
@bep bep added this to the v0.62.1 milestone Dec 27, 2019
bep added a commit to bep/hugo that referenced this issue Dec 28, 2019
@bep bep closed this in #6679 Dec 28, 2019
bep added a commit that referenced this issue Dec 28, 2019
Fixes #6677
@Kissaki

This comment has been minimized.

Copy link

@Kissaki Kissaki commented Jan 3, 2020

It would be helpful if the commit message were self-contained and pointed out what it changes.

Atm. from the release page I can look at the commit and this ticket and see nothing. Then I have to navigate to a forum which has some reproduction case, some reasoning and some caveats split up into several posts.

It would be much appreciated if the Git commit or at least the bug ticket it references were self-contained and explanatory.

@bep

This comment has been minimized.

Copy link
Member Author

@bep bep commented Jan 3, 2020

There is 1) What: "inline shortcodes" 2) A failing test case now fixed. That is both self-contained and explanatory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.