Closed mikecann closed 3 years ago
@mikecann It looks like this is because we're currently spreading the props that are passed to the component to allow users to specify additional attributes (className, id, etc...). This shouldn't have any effect on the functionality, but it would probably be best to filter out the config object before passing it to the JSX element.
Ah okay no worries :) Feel free to close this.
Describe the bug
It seems like the config object is being searialised into a HTML attribute
Usage like:
Example found: https://mikecann.co.uk/posts/the-cube
Any ideas?