-
Notifications
You must be signed in to change notification settings - Fork 816
Additional div rendered? #227
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
Comments
Guys, it took too much time to be fixed this and I've forked and created my own version to fixed. I've also opened a pull request on this repo, let's see if they'll merge it, eventually. The pull request: My branch with the fix: My branch with built files, in order to use it with npm (or yarn or whatever): To use it directly you can add it like this:
|
After running into this problem myself, and seeing that it's unlikely to be resolved here, I "solved" it by using |
I noticed that the component renders an additional DIV in the GoogleApiComponent file during the render (see line 119 in file).
Why not add ability for
className
on this DIV or use a different sort of wrapper using something like:const wrapper = (props) => props.children;
So the additional
div
is not rendered? Or is there a reason adiv
was used?The text was updated successfully, but these errors were encountered: