fix(gatsby-transformer-remark): Handle headings with nested text

[diegohaz]

Description

Here's a fix. If there's a better way to write the solution, just let me know.

Related Issues

Fixes #11879

[DSchau]

Nice idea here with this failing test 👏

[stefanprobst]

I'm sorry I missed this one before #11888
Anyway, we should make sure headings like the following are handled correctly:

# An **important** heading with `inline code` and text

[stefanprobst]

@diegohaz I'll close #11888 in favor of this. We probably want to use mdast-util-to-string here, which handles formatted text as well as inlineCode.

[diegohaz]

Thank you @stefanprobst. Added a test case with your example and fixed with mdast-util-to-string.

[sidharthachatterjee]

Thank you @diegohaz 👍

[gatsbot]

Holy buckets, @diegohaz — we just merged your PR to Gatsby! 💪💜

Gatsby is built by awesome people like you. Let us say “thanks” in two ways:

1. We’d like to send you some Gatsby swag. As a token of our appreciation, you can go to the Gatsby Swag Store and log in with your GitHub account to get a coupon code good for one free piece of swag. (Currently we’ve got a couple t-shirts available, plus some socks that are really razzing our berries right now.)
2. We just invited you to join the Gatsby organization on GitHub. This will add you to our team of maintainers. Accept the invite by visiting https://github.com/orgs/gatsbyjs/invitation. By joining the team, you’ll be able to label issues, review pull requests, and merge approved pull requests.

If there’s anything we can do to help, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’.

Thanks again!

[sidharthachatterjee]

Published in gatsby-transformer-remark@2.2.6