-
-
Notifications
You must be signed in to change notification settings - Fork 185
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
Conversation
3af1a63
to
92777e2
Compare
c8ce86d
to
f0ad74f
Compare
@danth, What do you think of optional 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. |
f950658
to
e6d3fd8
Compare
@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. |
e6d3fd8
to
f7df7f3
Compare
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. |
3391373
to
096b3f0
Compare
096b3f0
to
dfe24d5
Compare
i believe i've put the testbeds in the right location for when it is. |
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.
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.
resolved! |
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.
LGTM.
Waiting on #858 to merge this PR.
Note that with the current state of #858, the testbeds will end up being named Not sure if this is really an issue or I'm just being picky. |
I think that this would be better, if possible |
Actually, indicating in the testbed name that the |
Depends on whether we want to match the target name (improves user experience) or the module name (improves developer experience). |
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.
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.
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:
stylix/docs/src/configuration.md
Lines 207 to 211 in 73bcf4a
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.
@trueNAHO did you mean to request changes? I don't see anything else which needs to be done. |
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.
@trueNAHO did you mean to request changes? I don't see anything else which needs to be done.
My bad. This PR LGTM.
Link: danth#854 Reviewed-by: Daniel Thwaites <[email protected]> Reviewed-by: NAHO <[email protected]>
Link: danth#854 Reviewed-by: Daniel Thwaites <[email protected]> Reviewed-by: NAHO <[email protected]>
Link: #885 Fixes: 7feb1c2 ("discord: combine nixcord, vencord, and vesktop modules (#854)") Reviewed-by: NAHO <[email protected]>
Link: danth#885 Fixes: 7feb1c2 ("discord: combine nixcord, vencord, and vesktop modules (danth#854)") Reviewed-by: NAHO <[email protected]>
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.