diff options
| author | Maximilian Bosch <maximilian@mbosch.me> | 2021-07-23 10:56:24 +0200 |
|---|---|---|
| committer | Maximilian Bosch <maximilian@mbosch.me> | 2021-08-25 23:18:27 +0200 |
| commit | b6d3c9f821b704fbfb68d20a76520fa9e160df36 (patch) | |
| tree | 08aef81024286917fbc0f617b1796e800e4cf026 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | fbc9084c39297f6a8ca618b0f6a3ccdd4489ab6a (diff) | |
lib/modules: fix error-message when declaring an option inside `config'
The message I originally implemented here was to catch a mixup of
`config' and `options' in a `types.submodule'[1]. However it looks
rather weird for a wrongly declared top-level option.
So I decided to throw
error: The option `foo' does not exist. Definition values:
- In `<unknown-file>':
{
bar = {
_type = "option";
type = {
_type = "option-type";
...
It seems as you're trying to declare an option by placing it into `config' rather than `options'!
for an expression like
with import ./lib;
evalModules {
modules = [
{
foo.bar = mkOption {
type = types.str;
};
}
];
}
[1] fa30c9abed61f30218a211842204705986d486f9
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions
