#2 No easy way to link an extension to a user account.

Open
opened 1 year ago by Moonchild · 2 comments
Moonchild commented 1 year ago

There doesn’t seem to be an easy way to find out from an extension view which user account has uploaded it? I may be missing something obvious of course but if one wanted to check an unreviewed add-on then contact the user who uploaded it, e.g. to give feedback on incorrect install.rdf use, too long “short” description or what not, then that can’t easily be done.

I think being able to easily contact the uploader from the extension screen will be important as the number of extensions and users grows.

There doesn't seem to be an easy way to find out from an extension view which user account has uploaded it? I may be missing something obvious of course but if one wanted to check an unreviewed add-on then contact the user who uploaded it, e.g. to give feedback on incorrect install.rdf use, too long "short" description or what not, then that can't easily be done. I think being able to easily contact the uploader from the extension screen will be important as the number of extensions and users grows.
Ghost commented 1 year ago

There is no real way to do this in this design.

There is no real way to do this in this design.
Ghost closed this issue 1 year ago
Moonchild reopened this issue 3 months ago
Moonchild commented 3 months ago
Owner

There is no real way to do this in this design.

I don’t believe this is the case.
slugs are stored on user accounts as an array of text; while not optimal for query purposes, this won’t be a hot path (only used in administration). Alternatively, the db could be adjusted to have this information stored in the addon table instead of the user table as it’s a 1:1 relation, and actually makes more sense there.

> There is no real way to do this in this design. I don't believe this is the case. slugs are stored on user accounts as an array of text; while not optimal for query purposes, this won't be a hot path (only used in administration). Alternatively, the db could be adjusted to have this information stored in the addon table instead of the user table as it's a 1:1 relation, and actually makes more sense there.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.