On Tue, 13 Nov 2018 at 16:01, <makep...@firemail.cc> wrote: > Please consider sending a pull request to ts-for-gjs with definitions > and tests for registerClass, if you have time before I can write them. > It's a relatively new thing, haven't needed it yet. So far the focus has > been on GObject introspection. Definitions for other built-ins, such as > package, signals and system, would be helpful too. >
I would quite like to try this after all, but I'm not sure of the best way to do it. I don't really like the idea of hard-wiring just the bits I'm interested in, it would be better to add some sort of reusable overrides system. But I think it would be OK to keep it very simple, basically a map keyed by module name with the values consisting of a string of extra lines of code to add to the .d.ts. Or would you prefer something more sophisticated such as separate lists for functions, symbols etc? -- TH
_______________________________________________ javascript-list mailing list javascript-list@gnome.org https://mail.gnome.org/mailman/listinfo/javascript-list
