lib/modules: add evalNixvim

[MattSturgeon]

Evaluates a nixvim config, by default also checking warnings and assertions.

This used internally by the standalone wrapper.

I'm planning to use this to refactor the tests implementation:

• The tests don't need a "full" standalone build
• The tests should be able to expect/reject warnings/assertions
• Warnings should fail tests (unless marked as expected)

But I figured it'd be easier to test/review if I push this as a separate PR.

[MattSturgeon]

Looking at the implementations in #1986 and #1989, I'm wondering if the interface here is a little over-engineered?

I think the only place where we'd use it with the default values would be the standalone wrapper 🫤

[MattSturgeon]

Looking at the implementations in #1986 and #1989, I'm wondering if the interface here is a little over-engineered?

This is resolved in the latest force-push, however I still think we can simplify things further by moving the warning/assertion handling to finalPackage's evaluation; similar to how nixos checks warnings/assertions while evaluating the activation package option.

EDIT: maybe this wouldn't make sense, since we don't want to check assertions/warnings on hosted wrappers, instead we pass our assertions/warnings up to the host's option...

[MattSturgeon]

@Mergifyio queue

[mergify]

queue

✅ The pull request has been merged automatically

Details

The pull request has been merged automatically at 851edc8