-
Notifications
You must be signed in to change notification settings - Fork 19
Issues: gjsify/ts-for-gir
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Missing promisified overloads
bug
gjs-convention
Marks issues for aligning with GJS coding standards and practices
#171
opened May 5, 2024 by
JumpLink
Requires
property is missing on MetaInfo
gjs-convention
#166
opened Apr 29, 2024 by
naipotato
Some nullable object properties are not marked as nullable by TS for GIR
#156
opened Mar 17, 2024 by
YarnSphere
Incorrect types for Marks issues for aligning with GJS coding standards and practices
Gio.BindingTransformFunc
gjs-convention
#154
opened Mar 13, 2024 by
vixalien
Incorrect types for Marks issues for aligning with GJS coding standards and practices
Gio.ActionMap.add_action_entries
gjs-convention
#153
opened Mar 13, 2024 by
vixalien
When constructing Marks issues for aligning with GJS coding standards and practices
St.Widget
, specifying layout_manager
(as a subclass of LayoutManager
) should be reflected in types
gjs-convention
#145
opened Feb 11, 2024 by
KSXGitHub
Configure additional async functions
gjs-convention
Marks issues for aligning with GJS coding standards and practices
#140
opened Nov 25, 2023 by
swsnr
Handle new attributes of gobject-introspection
gjs-convention
Marks issues for aligning with GJS coding standards and practices
#115
opened Apr 11, 2023 by
JumpLink
Type definitions that are necessary to not produce type errors should be marked
#93
opened Sep 26, 2022 by
JumpLink
Inherited or implemented event / signal types are not available
node-gtk-convention
Marks issues for aligning with node-gtk coding standards and practices
#75
opened Jul 1, 2022 by
JumpLink
ProTip!
Follow long discussions with comments:>50.