getsentry / getsentry/sentry

Project name used incorrectly

Open
#47,396 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
1d 5h
Merged PRs (30d)
624

Description

The 'name' column on Project was deprecated a LONG time ago, but somehow has made its way back fully propagated, and now also incorrectly.

At one point in history we deprecated the name column in favor of slug, and at that point we removed name from the configuration. It was intended that slug was more than enough of an identifier (and confusing when it was wildly different than name).

I noticed this because an internal project (vanguard) had a slack notification, and the notification included the project name. That project name was set to Next.js, likely because I had selected Next.js when first creating the project. However that project's slug has always been vanguard for as long as I can remember.

The name column should be completely deprecated, references replaced with the slug, and not be visible in the UI.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.