Colin McDonnell

Check for instance before confirmation prompt on `instance delete`

1

``` $ edgedb instance destroy -I nonexistent_instance Do you really want to delete instance "nonexistent_instance"? (type `Yes`) > Yes edgedb error: instance not found: instance not found ```

Hide revision hashes from user-facing messages

2

Before ``` $ edgedb migration create Created dbschema/migrations/00003.edgeql, id: m1yh4d3dmfghpbidcnh3jf3flusvznborapmb54blv5mloiqzuzsia edgedb migrate Applied m1yh4d3dmfghpbidcnh3jf3flusvznborapmb54blv5mloiqzuzsia (00003.edgeql) ``` After ``` $ edgedb migration create Created dbschema/migrations/00003.edgeql. $ edgedb migrate Applied dbshcema/migrations/00003.edgeql. ```

It would make it easier to document/explain certain things if there was a way to get a particular path from `edgedb info`. Currently: ```bash $ edgedb info [2022-08-16T19:02:15Z WARN edgedb::version_check]...

Detect project for `edgedb instance` commands

2

Latest nightly seems not to detect projects for `edgedb instance` commands. Running inside an initialized project: ``` $ edgedb EdgeDB 2.0-dev.6625+f62dc75 (repl 1.2.0-dev.783+6690d4d) Type \help for help, \quit to quit....

Deprecate instance name argument in favor of flag

10

Per the team call: - Deprecate the passing of an instance name argument (`edgedb instance stop myinst`) in favor of a flag (`edgedb instance stop -I myinst`). Support for passing...

Implement semver version pinning in `edgedb.toml`

1

Currently `edgedb.toml` only supports major version pinning, but with the switch to portable builds we can now support full semver versioning. Per https://edgedb.slack.com/archives/CNECHA9EW/p1647542994504509

Prevent deletion of edited queries with down array

1

When you use :arrow_up: to see the last query, make some edits, then press the down arrow, it deletes the query and you lose your changes. Ideally, after edits are...

Writing queries in REPL then copying into actual code is a common use case. Currently copying a query on macOS also includes the `......` at the start of the line....

Obsolete approach

1

PSA for the community: since the release of Next.js 9.5 the custom server (`/server.js`) approach to this is no longer recommended by the Next.js team. Instead you should use `rewrites`...

Before merging: - [ ] Implement support for `EDGEDB_SERVER_TLS_CERT{_ENV}`/`EDGEDB_SERVER_TLS_KEY{_ENV}` in `edgedb-server`. Currently only the `_FILE` variant is supported.