-
-
Notifications
You must be signed in to change notification settings - Fork 438
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
I do not care about this project anymore, will accept only issues with PR. #3300
Comments
What would be the best way someone could help right now? I got some free time and this project has been enormously helpful to me, so where could you use the most help? :) |
@JustFly1984 We appreciate all your hard work on this project but one thing to consider before abandoning it is a tenant from The_Cathedral_and_the_Bazaar...
|
@wmessino There is a need to update config for docs: https://react-docgen.dev/docs/migrate/v6, cos in current state it doesn't build. |
That's totally fair. Appreciate your work over the years and probably most people should just move to https://visgl.github.io/react-google-maps/ once it lands a stable 1.0. |
Until there will be something better, it is ok to use this one. If you want to be compatible with nextjs, you should use it in client components. |
I really appreciate your work on this library, it was plug-and-play and I'm sure it saved me a bunch of work hours 🥇 It could be nice if you added this information to the readme.md or the issue template btw? Oh wait, I'm doing it again 🙈 Let's try this: Here is a PR which adds information to the issue template: #3333 😅 |
Until there will be something better, it is ok to use this one. If you want
to be compatible with nextjs, you should use it in client components.
…On Thu, 16 Nov 2023 at 4:17 PM, Michael Buss Rønne ***@***.***> wrote:
That's totally fair. Appreciate your work over the years and probably most
people should just move to https://visgl.github.io/react-google-maps/
once it lands a stable 1.0.
—
Reply to this email directly, view it on GitHub
<#3300 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AARGY6LBBOXPCWC33Z2G2PDYEXK2LAVCNFSM6AAAAAA5ZOHPNGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJUGA3DCMJSGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Ok, I'm back, released 2.20.0 and consequently 2.20.1 |
I see some issues, but I see no PRs. I do not need this project for any of my own projects for a long time. If I will have to use it, I will invest more time in it, but by now nobody is caring about it except me. Since now, I will accept only issues with codesandbox reproduction and PR with solution.
The text was updated successfully, but these errors were encountered: