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
riot-web conf override broken #81416
Comments
I think the change intentionally broke compatibility; maybe this should not have been backported to stable. In any case you should rewrite the |
I liked the fact that I could simply copy/paste JSON into my config and edit it directly. |
Ohh, that's right. I wish I looked at things a bit closer before backporting that to 19.093 |
c9e5cca changed the type from str to attrset, which broke some people's config. GitHub: closes NixOS#81416
the conf override is also broken for attrset itself, please check #81452 |
It's not. See #81452 (comment). |
f18d4e3 changed the type from str to attrset, which broke some people's config. GitHub: closes NixOS#81416
@pacien can you add a release note for 20.03 that mentions the breaking change? |
For the release notes: #81473 |
Mention the changes introduced in commit c9e5cca. GitHub: closes NixOS#81416
Describe the bug
Since f18d4e3 overriding
riot-web
with a string is no longer possible as it expects an attrset now.To Reproduce
Steps to reproduce the behavior:
have
pkgs.riot-web.override { conf = ''{ "foo": "bar" }'' };
in a configExpected behavior
overriding with strings is still possible
@pacien
The text was updated successfully, but these errors were encountered: