You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently the cue fmt utility will indent the closing triple-quote for a multi-line string, e.g.
Thing: MyValue: ###"""
Stuff
"""###
}
will be shifted to:
Thing: MyValue: ###"""
Stuff
"""###
}
^ notice the closing quote and string body is now tab indented.
this can be problematic for users, including myself, who are copy/pasting data between this cue file and some other system.
let's say excel ... that you copy/paste the value from an excel field into here, then save or run your script (which probably format), and now it's not what you pasted anymore, but you make some edits in your cue ide of choice, then copy & paste it back ... well ... that's a whole can a problems ... but say it works, then you copy/paste it back ... well, maybe it's not valid any more since the value now contains tabs which aren't allowed in your excel field (and for good reason). or ... maybe instead of excel it's a different editor which is 'kind' enough to convert your pasted tabs back into spaces ... so now when you paste it back into cue, you don't have a leading tab anymore so it's not valid and cue will error.
i agree the nesting looks nicer, but this is a total usability nightmare waiting to happen, so there needs to be some way to manage this behaviour.
but this seems subtly different, maybe it's a request for an alternate syntax or requiring a raw string (to prevent escaping issues), a field attribute or something else.
not sure how to file this, but capturing.
currently the cue fmt utility will indent the closing triple-quote for a multi-line string, e.g.
will be shifted to:
^ notice the closing quote and string body is now tab indented.
this can be problematic for users, including myself, who are copy/pasting data between this cue file and some other system.
let's say excel ... that you copy/paste the value from an excel field into here, then save or run your script (which probably format), and now it's not what you pasted anymore, but you make some edits in your cue ide of choice, then copy & paste it back ... well ... that's a whole can a problems ... but say it works, then you copy/paste it back ... well, maybe it's not valid any more since the value now contains tabs which aren't allowed in your excel field (and for good reason). or ... maybe instead of excel it's a different editor which is 'kind' enough to convert your pasted tabs back into spaces ... so now when you paste it back into cue, you don't have a leading tab anymore so it's not valid and cue will error.
i agree the nesting looks nicer, but this is a total usability nightmare waiting to happen, so there needs to be some way to manage this behaviour.
also relates to:
#834
#1033
#1720
but this seems subtly different, maybe it's a request for an alternate syntax or requiring a raw string (to prevent escaping issues), a field attribute or something else.
also further compounded by: monogon-dev/intellij-cue#55
The text was updated successfully, but these errors were encountered: