-
Notifications
You must be signed in to change notification settings - Fork 18
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
ts-for-gir and gi.ts #120
Comments
@marcinjahn yes it is so. When I started this project, gi.ts was not working, so I couldn't test it, otherwise I would have contributed there. Instead I contributed to this project which was originally initiated by @sammydre and I took over with time. I think now we can try different things in both projects and in the end maybe implement the best practices and maybe merge the projects again. Currently this project has a few features that I need for my projects, so I don't want to give it up. Both projects generate already very good typescript types whereby both have their strengths in small details. |
Hi 👋 I started gi.ts in 2019 when from what I gathered at the time this project had gone inactive. At that point the type definitions produced by this project did not accurately reflect GJS and weren't usable in my projects (e.g. typechecking gnome-shell and GJS itself) and I wanted to try rebuilding aspects of the type generation from the ground-up. Since then, @JumpLink has done a great work with this project while I have also made incremental updates to gi.ts. As @JumpLink points out, each project has its strengths and weaknesses when it comes to fully supporting GJS' APIs and features. At this point, I hope we can find a way to unify the projects so the community benefits and we can work together on improvements going forward. I'll ping you on Matrix @JumpLink 😺 |
Work in progress on #144 |
I'd like to understand what is the difference between this project and https://gitlab.gnome.org/ewlsh/gi.ts/-/tree/master/?
Are these two separate projects that tackle the same problem?
The text was updated successfully, but these errors were encountered: