Skip to content
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

aerospace: fix on-window-detected #1168

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

talhaHavadar
Copy link

@talhaHavadar talhaHavadar commented Nov 14, 2024

This fixes the issue #1142

I am not proficient in nix so I tried to create a sort of generic type, it might be too broad in this case but this fixes the Aerospace crash issue due to incorrect typing.

@talhaHavadar talhaHavadar force-pushed the fix-aerospace-on-window-detect branch from 44a46ea to 0a3df54 Compare November 14, 2024 19:11
@jnsgruk
Copy link

jnsgruk commented Nov 15, 2024

Would be nice to land this! Is there anything I can do to help?

@talhaHavadar
Copy link
Author

actually had no idea how to speed things up, this is my first time contributing this repo.

@@ -71,9 +85,17 @@ in
description = "Default orientation for the root container.";
};
on-window-detected = lib.mkOption {
type = listOf str;
type = listOf (attrsOf (either callbackConf (listOf callbackConf)));
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be better with types.listOf (types.attrsOf types.anything)

Ideally we would be able to type this better, but I'm not familiar with Aerospace

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is cleaner indeed :) just pushed the changes

@talhaHavadar talhaHavadar force-pushed the fix-aerospace-on-window-detect branch from 7f5231c to 8259566 Compare December 2, 2024 09:44
@z0al
Copy link
Contributor

z0al commented Dec 5, 2024

fyi, this PR is older but #1168 #1208 is more complete

@talhaHavadar
Copy link
Author

I don't really have any idea how the fix is being managed really :)

@z0al
Copy link
Contributor

z0al commented Dec 5, 2024

@talhaHavadar my bad. I linked the wrong pr by mistake 😓 . Here is the correct pr #1208

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants