Hey XIII ,
While we look into the issue, I've found a temporary workaround in setting field values to contain newlines via the CLI.
I understand my solution is not ideal as it is quite inconvenient, but it may serve you for the time being while we sort things out.
You can set the values into a temporary variable:
export VALUE_WITH_NEWLINES="A\nb\n3"
And interpolate the variable into the op item edit or op item create commands:
op item edit exampeItem "section1.field1[text]=$(echo $VALUE_WITH_NEWLINES)"
By the way, I noticed you wrote "(as before)" in your original post, I am wondering if newlines had worked for you in setting field values in the CLI v1? I ask because I have not been able to do so, for example:
op1 create item login --vault demo --title exampleItem notesPlain="A\nb\n3"
Results in a username field that also contains the raw \n chars instead of newlines.
I share Horia's sentiment - thank you for the feedback!
