tests/modules/lsp: fix package-fallback assertion logic

The "is in" vs "isn't in" logic was accidentally inverted.

(cherry picked from commit 03a638205b)
This commit is contained in:
Matt Sturgeon 2026-01-15 13:37:14 +00:00 committed by Gaétan Lepage
parent 983751b66f
commit 503259b749
2 changed files with 6 additions and 6 deletions

View file

@ -196,21 +196,21 @@
let
assertPrefix = name: pkg: [
{
assertion = lib.all (x: x == pkg) config.extraPackages;
assertion = lib.elem pkg config.extraPackages;
message = "Expected `${name}` to be in extraPackages";
}
{
assertion = lib.any (x: x != pkg) config.extraPackagesAfter;
assertion = !(lib.elem pkg config.extraPackagesAfter);
message = "Expected `${name}` not to be in extraPackagesAfter";
}
];
assertSuffix = name: pkg: [
{
assertion = lib.all (x: x != pkg) config.extraPackages;
assertion = !(lib.elem pkg config.extraPackages);
message = "Expected `${name}` not to be in extraPackages";
}
{
assertion = lib.any (x: x == pkg) config.extraPackagesAfter;
assertion = lib.elem pkg config.extraPackagesAfter;
message = "Expected `${name}` to be in extraPackagesAfter";
}
];

View file

@ -264,11 +264,11 @@
let
assertAfter = name: pkg: [
{
assertion = lib.all (x: x != pkg) config.extraPackages;
assertion = !(lib.elem pkg config.extraPackages);
message = "Expected `${name}` not to be in extraPackages";
}
{
assertion = lib.any (x: x == pkg) config.extraPackagesAfter;
assertion = lib.elem pkg config.extraPackagesAfter;
message = "Expected `${name}` to be in extraPackagesAfter";
}
];