Stringify metadata object for html content

[quartusk]

When the optional metadata object is passed, the object was never converted to a string representation, which results in the html content using the default serialization and looking like this:

metadata: [object Object]

After applying JSON.stringify to the object, we'll get a valid string representation:

metadata: {"custom_fields":[{"display_name":"Test Custom Field","variable_name":"test_custom_field","value":"Test Value"}]},

[just1and0]

Hi @quartusk good spot! I will approve once it passes CI checks.

I would also recommend you read the contribution docs to better understand how to name your commits.

This is important as CI will not publish your changes to npm if this isn't done right.

[quartusk]

Sorry I missed the CONTRIBUTING.md at first glance. I can create a new pull request if that helps speed things up

[just1and0]

Nah you don't need a new pr
You can make an empty space and commit that. But make sure it's the right commit title.

And that should do it

[quartusk]

Thanks, I've amended the commit message

[just1and0]

@all-contributors add @quartusk for code

[allcontributors]

@just1and0

I've put up a pull request to add @quartusk! 🎉

[github-actions]

🎉 This PR is included in version 4.6.7 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀