🧩 FEATURE REQUEST: Ability to name shortcuts

[nick-ollier]

Concise Description

Add the ability to name shortcuts.

Description

When adding a shortcut - All that is visible is a snippet of the URL and an icon. When adding shortcuts to the same website, the feature becomes more of a hindrance as at a glance you're unable to distinguish which shortcut is which.

This screenshot isn't my own but it highlights the problem quite nicely.

Solution Proposed

Add the ability to include a name when adding a shortcut.

Additional Context

Code of Conduct

• I follow the conditions of this project.

[sabdailydev]

@nick-ollier Yes , the experience can be made better by allowing users to edit the shortcut. We will accept the issue and open it for community contribution.

[NiteshSingh17]

@sabdailydev The current schema is an array of strings. If we change it to an array of objects that include labels, it will break compatibility for existing users.

[nick-ollier]

👋🏻 @NiteshSingh17

I think the schema for shortcuts could be updated to support a heterogeneous union fairly easily. This would allow each shortcut to render conditionally based on whether it's a string[] -or- { name: string; url: string; anythingElse: any }[]. This would also support backwards compatibility as it wouldn’t affect any existing shortcuts and would allow new ones to be added in the updated format.

Working example:
⚡️ Stackblitz

Screenshot

[NiteshSingh17]

👋🏻 @nick-ollier

Thanks for your comment! I also think this might be a simple and easy way to solve the issue. However, I have one concern with this approach it introduces data ambiguity into our schema, which could become problematic in the future.

In my opinion, the best approach would be to update the existing data to support the new schema. I agree that suggested solution carries some risks.

It might be helpful if someone from the daily.dev team could also share their thoughts on how to best resolve this.