Skip to content

cmp: use normal priority for default of sources #884

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

Merged
merged 1 commit into from
May 6, 2025

Conversation

horriblename
Copy link
Collaborator

fixes #839

After this change, user configs are "appended" to default ones
instead of overriding them

After this change, user configs should be "appended" to default ones
instead of overriding them
github-actions bot pushed a commit that referenced this pull request May 5, 2025
Copy link

github-actions bot commented May 5, 2025

🚀 Live preview deployed from 10a06b3

View it here:

Debug Information

Triggered by: horriblename

HEAD at: cmp-sources-normal-prio

Reruns: 805

@NotAShelf
Copy link
Owner

This will force the users to always use mkForce to allow our defaults. The default behaviour should be overridable without such a headache imo.

@horriblename
Copy link
Collaborator Author

based on how long it took for #839 to be resolved I would disagree, people expect the default value to be extended rather than overwritten

alternatively, we could write it down somewhere how listOf/attrsOf options are expected to work

@NotAShelf
Copy link
Owner

Okay, let's get this fix out of the way and revisit the underlying issue again in the future. I think explicit override is a sensitive matter, and I'd like to discuss it when I have less on my plate.

@NotAShelf NotAShelf merged commit d3c7f71 into NotAShelf:main May 6, 2025
13 of 14 checks passed
Copy link

github-actions bot commented May 6, 2025

✅ Preview has been deleted successfully!

NotAShelf added a commit that referenced this pull request May 6, 2025
…prio"

Reverts commit d3c7f71, reversing
changes made to f07468e.
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.

Path error after updating flake.lock
2 participants