Yury Selivanov
Yury Selivanov
> IMO, they should be proper literals. Yep. And then we can syntax highlight the input.
> That sounds like over-engineering: the primary use case for the feature is to quickly past query from the code an fill in the gaps. Yes, but if the query...
> And also convenience goes away with it. Not really, I'm fine with typing proper string literals in REPLs. In EdgeDB repl, in Python repl, etc. I really don't understand...
> If we go with "json_parameters" we: > We don't have type info about parameter (so can't provide a shortcut for datetime_current() for example) We can have type info about...
> I'd say we may have a partial json_parameters mode that only wraps unknown types (either explicitly selectively or implicitly all unknown types). Not sure how hard is that in...
> Native literals, but not default for simple types like numbers and strings I still think that strings should require explicit quotes, e.g. ``` $foo > 'aaa' ``` > Basically...
> unclear what to do if they do enter quotes, i.e do we double-quote them or assume the value as-is? This is why I don't like the idea of "simplifying"...
@fantix were you working on this?
https://github.com/clap-rs/clap/issues/1431 -- looks like it's not there yet. We might need to contribute a fix to clap.
How do you want to implement this? I see two options: 1. real time, as messages are received they are displayed, even if the user is typing a query. 2....