Create new attributes inside lambda

[tomberek]

Situation:

{
  outputs = {...}: {
     a = {};
  };
}

Running nix-editor test.nix outputs.a -v 1 produces:

{
  outputs = {...}: {
     a = 1;
  };
}

as expected. But nix-editor test.nix outputs.a.b -v 1 produces:

{
  outputs = {...}: {
     a = {};
  };
  outputs.a.b = 1;
}

where the attrset was not placed into the function call, but on the outside.

[vlinkz]

Should be fixed in 6f33bad and 7b0af65, although indentation is still hackish

[tomberek]

This still seems to be an issue. Querying for values inside the lambda works as expected, but the traversal for writing doesn't seem to use the same logic.

$ cat test.nix
{
  outputs = inputs: inputs.d {
    a.b = {};
  };
}
$ nix-editor test.nix outputs.a
{ b = { }; }

$ nix-editor test.nix outputs.a.b -v 1
{
  outputs = inputs: inputs.d {
    a.b = {};
  };
  outputs.a.b = 1;
}

$ nix-editor test.nix outputs.a.c -v 1
{
  outputs = inputs: inputs.d {
    a.b = {};
  };
  outputs.a.c = 1;
}

[tomberek]

Latest changes (ab2a7e9):

nix-editor test.nix outputs.a.b -v '{v=1;}'
{
  outputs = inputs: inputs.d {
    a.b = {};
  };
  outputs.a.b = {v=1;};
}

and

nix-editor test.nix outputs.a.b -v 'true'
{
  outputs = inputs: inputs.d {
    a.b = {};
    a.b = true;
  };
}

[vlinkz]

Hm yeah, that seems to have to do with the way attribute sets are handled differently than values

[tomberek]

work-around with an empty flake

nix-editor test.nix outputs.a.b -v 'rec {c=1;}'
{
  outputs = inputs: inputs.d {
    a.b = rec {c=1;};
  };
}

This seems to bypass the "{" detection logic.