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

discord: combine nixcord, vencord, vesktop #854

Merged
merged 2 commits into from
Feb 17, 2025

Conversation

Flameopathic
Copy link
Contributor

@Flameopathic Flameopathic commented Feb 10, 2025

combines the nixcord, vencord, and vesktop hm.nix modules into one.

handles the config separately as the nixcord module requires odd conditions for evaluation.

unsure how to handle the testbeds.

@Flameopathic Flameopathic marked this pull request as draft February 10, 2025 20:56
@Flameopathic Flameopathic force-pushed the discord-module branch 2 times, most recently from c8ce86d to f0ad74f Compare February 10, 2025 20:59
@trueNAHO
Copy link
Collaborator

trueNAHO commented Feb 10, 2025

unsure how to handle the testbeds.

@danth, /modules/firefox/ suffers from the same problem of having one testbed per module, although multiple testbeds would be beneficial.

What do you think of optional /modules/<MODULE>/testbeds/<TESTBED>.nix testbeds, while asserting that /modules/<MODULE>/testbed.nix should not exist while any /modules/<MODULE>/testbeds/<TESTBED>.nix exists. However, this prevents the use of a highly convenient local /modules/<MODULE>/testbeds/common.nix abstraction. Either, we handle certain file names differently (probably a bad idea) or such files are expected to go to /modules/<MODULE>/common.nix. Since we are looking for specific files and directories inside /modules/<MODULE>/, adding arbitrary named files in this scope does not cause problems.

Note that implementing this functionality should probably not fall in the scope of this PR. It should be fine to keep only one testbed in this PR and add the others back once this functionality is implemented.

@Flameopathic Flameopathic force-pushed the discord-module branch 2 times, most recently from f950658 to e6d3fd8 Compare February 11, 2025 02:28
@Flameopathic Flameopathic marked this pull request as ready for review February 11, 2025 02:33
@danth
Copy link
Owner

danth commented Feb 11, 2025

@trueNAHO That sounds reasonable. Ignoring specific file names would be confusing and limiting, so I agree, it's better to just import from the parent directory when some shared code is needed.

@trueNAHO
Copy link
Collaborator

Btw, I am currently working on #854 (comment) and will finish it up tomorrow.

@trueNAHO
Copy link
Collaborator

Btw, I am currently working on #854 (comment) and will finish it up tomorrow.

If we wait for #858 to get merged, we can keep all testbeds in this PR.

@Flameopathic Flameopathic force-pushed the discord-module branch 2 times, most recently from 3391373 to 096b3f0 Compare February 12, 2025 02:30
@Flameopathic
Copy link
Contributor Author

If we wait for #858 to get merged, we can keep all testbeds in this PR.

i believe i've put the testbeds in the right location for when it is.

Copy link
Collaborator

@trueNAHO trueNAHO left a comment

Choose a reason for hiding this comment

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

If we wait for #858 to get merged, we can keep all testbeds in this PR.

i believe i've put the testbeds in the right location for when it is.

I just realized that I intended the testbed directory to be called testbeds instead of testbed: f79d6cf93e0b..482525df19c8.

Otherwise, this PR LGTM once #858 is merged.

@Flameopathic
Copy link
Contributor Author

I just realized that I intended the testbed directory to be called testbeds instead of testbed: f79d6cf93e0b..482525df19c8.

resolved!

Copy link
Collaborator

@trueNAHO trueNAHO left a comment

Choose a reason for hiding this comment

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

LGTM.

Waiting on #858 to merge this PR.

@danth
Copy link
Owner

danth commented Feb 12, 2025

Note that with the current state of #858, the testbeds will end up being named testbed-discord-{vencord,vesktop}, which doesn't correspond with the stylix.targets.{vencord,vesktop} options. Personally I would expect the testbeds to be named testbed-{vencord,vesktop} as they are separate targets.

Not sure if this is really an issue or I'm just being picky.

@Flameopathic
Copy link
Contributor Author

Personally I would expect the testbeds to be named testbed-{vencord,vesktop} as they are separate targets.

I think that this would be better, if possible

@trueNAHO
Copy link
Collaborator

testbeds will end up being named testbed-discord-{vencord,vesktop}, which doesn't correspond with the stylix.targets.{vencord,vesktop} options. Personally I would expect the testbeds to be named testbed-{vencord,vesktop} as they are separate targets.

[...]

Not sure if this is really an issue or I'm just being picky.

Actually, indicating in the testbed name that the vencord and vesktop testbed variants are conceptually linked via the discord node seems like a bonus for me.

@danth
Copy link
Owner

danth commented Feb 16, 2025

Depends on whether we want to match the target name (improves user experience) or the module name (improves developer experience).

Copy link
Collaborator

@trueNAHO trueNAHO left a comment

Choose a reason for hiding this comment

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

Waiting on #858 to merge this PR.

This has been merged in commit 211a844.

Copy link
Owner

@danth danth left a comment

Choose a reason for hiding this comment

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

Looks good to me.


#858 adds to the documentation that testbeds should be named after the module, not the target: see this comment.

#873 also clarifies this on the user side:

You can discover the available targets and their options by browsing through
the module reference at the end of this book. Most targets will be found under
a module of the same name, but occasionally a module will serve multiple similar
targets. For example, the [Firefox module](options/modules/firefox.md) also
provides options for other browsers which are based on Firefox.

Hence the current naming of the testbeds should be fine.

@danth
Copy link
Owner

danth commented Feb 17, 2025

@trueNAHO did you mean to request changes? I don't see anything else which needs to be done.

Copy link
Collaborator

@trueNAHO trueNAHO left a comment

Choose a reason for hiding this comment

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

@trueNAHO did you mean to request changes? I don't see anything else which needs to be done.

My bad. This PR LGTM.

@trueNAHO trueNAHO merged commit 7feb1c2 into danth:master Feb 17, 2025
49 checks passed
pinarruiz pushed a commit to pinarruiz/stylix that referenced this pull request Feb 19, 2025
pinarruiz pushed a commit to pinarruiz/stylix that referenced this pull request Feb 19, 2025
trueNAHO pushed a commit that referenced this pull request Feb 21, 2025
Link: #885
Fixes: 7feb1c2 ("discord: combine nixcord, vencord, and vesktop modules (#854)")

Reviewed-by: NAHO <[email protected]>
Mikilio pushed a commit to Mikilio/stylix that referenced this pull request Feb 23, 2025
Link: danth#885
Fixes: 7feb1c2 ("discord: combine nixcord, vencord, and vesktop modules (danth#854)")

Reviewed-by: NAHO <[email protected]>
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.

3 participants