In validate_text function of the CLI (migrations.rs, line 64), it would be nice to tell users the file name that the CREATE MIGRATION appears in that needs to be changed, just to be clear that it’s in a file and which migration it applies to.
.withRetryOptions({attempts: 1})- This sounds like 1 retry attempt will be made, but if I understand the blog post on RC2 this actually suppresses even a single retry.
It’s intended to mean 1 attempt, not 1 retry attempt. Maybe this can be clarified in documentation. Probably hard to change at this point, and maybe doesn’t even make sense to change.
Should edgedb command line with no arguments and no edgedb.toml display help?
When schema changes, query builder has to be regenerated
Could the CLI handle this automatically when migrations are run for projects that use the query builder?
Some CLIs will print help when no options are passed. Since the EdgeDB CLI connects a console with the bare command (just edgedb), if it is run in a directory that is not a project, it shows an error.
Is there a way to balance the expectations of both developers who know the bare command tries to connect a console and users who may not be familiar with the CLI and might expect help from the bare command? Maybe connect the console only if in a project directory and show help otherwise? Or maybe show the error followed by the help? Maybe show something that looks less like an error but is more of a hint followed by help (e.g., “You ran edgedb in a directory that is not an EdgeDB project so we’re showing the CLI help. If this isn’t what you wanted, make sure you initialize a project in this directory.”)?
Automated uninstaller of the CLI? Current manual method requires a lot of steps (see Discord)
Better error message when trying to upgrade CLI first installed with Homebrew via edgedb cli upgrade