-
Notifications
You must be signed in to change notification settings - Fork 8
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
Port some types to GNOME 46 + some additional types #23
Conversation
Same as #22 these are just the Basics, and I have some complex types that are not correct yet, but those need some deep investigation, from where they come and how to fix them, and I am yet unsure, if they are from gnome shell or from other packages, @JumpLink you mentioned, that the generated types might be incorrect, or do I remember incorrectly? Anyways, I'll look into these, that might take some time |
@Totto16 yes, the existing types might not be correct. So if you think there might be something wrong, go ahead and change it |
@Totto16 In my MRs I marked every type which I added, update, or scrutinized for GNOME 46 with a I'm asking because I'm likely also going to touch the dialog modules when going through my extensions, so it'd help to see what's already been done. |
Yeah, that's a good idea, I am going to do this too 👍🏼 |
… methods and types
…, where I used an other Name
Edit: this is redundant, I removed it 👍🏼 This is ready now, I added something, that might be controversial, I can remove it, if you don't like it: it says So I thought, If it is a good idea, to type the returns of the Anyway, let me hear your opinion on that ❤️ |
public open(timestamp: number, onPrimary: boolean): boolean; | ||
public close(timestamp: number): boolean; | ||
public open(): boolean; | ||
//note: upstream has timestamp as paramater here, but it only will be used to call popModal, which doesn't accept that paramater anymore, so this is just a bug upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this issue reported to upstream and being fixed?
If so, why not add a link here? If not, perhaps report it, to clarify if it's a bug here or with popModal?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I intend to do that, but not yet 😓
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The bug is clearly here, since the last commits seem to get rid of the timestamp parameter everywhere else, they just missed it here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
made a MR on this issue: here
@Totto16 Thank you very much! Would you also be interested in becoming a maintainer? Then you could review and merge each other. It's a bit inconvenient that I'm not currently developing an extension myself 😅 |
Yeah for sure, that helps a lot. |
That makes me happy :) I have sent you an invite |
@JumpLink Not sure if it was meant to be implied here, but just in case there's a misunderstanding I'd like to point out that I am not a collaborator here and do not have permission to merge things here 🙂 I was just reviewing these changes because I'm interested 🙂 |
Send you an invite 📮 |
This ports some types to GNOME 46 and adds a new file:
ui/lightbox
This fixes only types, I need for an extension, and some things that changed, that I saw while doing that.