• Author: alrick
• Creation Date: May 15, 2020
• Reference Issues / Discussions:
  • https://github.com/directus/directus/discussions/2711

Summary

Allow users to rename collections and fields.

Basic Example

When using a PATCH to /collections or /fields, you should be able to update the collection and field property respectively. This will in turn change the value in both the database and all the system tables.

Motivation

Technical keys are a human created / entered value, which in turn means human errors sneak in. From cases as simple as typos to design decisions that have changed over time, errors will happen. The ability to rename is required to help users resolve these errors.

This is relevant for any admin user in any use case.

Detailed Design

API

The collection and field property of the collection and field object respectively needs to be writable in the input of the REST, GraphQL, WS, and SDK interfaces.

Edge Cases

There are some tricky edge cases like "collection item dropdown" storing the collection name in JSON interface options:

• collection item dropdown Is not a custom field, but one we provide in core

Custom Extensions:

• Include docs to indicate that any references to collection/fields in extensions will require updates

Requirements List