Skip to content

Generalize UserTagPicker#13080

Open
LiquidPL wants to merge 1 commit into
ppy:masterfrom
LiquidPL:generalize-tag-picker
Open

Generalize UserTagPicker#13080
LiquidPL wants to merge 1 commit into
ppy:masterfrom
LiquidPL:generalize-tag-picker

Conversation

@LiquidPL

Copy link
Copy Markdown
Contributor

RFC. I'm not sure if this is overkill and it'd be easier/cleaner to just copypaste the tag picker layout to a new component, so I'm PR'ing this in for discussion.

Intended to be used in a future PR allowing trusted users (and possibly other users in the future) to edit beatmap tags through web.

RFC. I'm not sure if this is overkill and it'd be easier/cleaner to just
copypaste the tag picker layout to a new component, so I'm PR'ing this
in for discussion.

Intended to be used in a future PR allowing trusted users (and
possibly other users in the future) to edit beatmap tags through web.
@import "bem/beatmap-discussions";
@import "bem/beatmap-discussions-header-bottom";
@import "bem/beatmap-discussions-header-top";
@import "bem/beatmap-user-tag-picker";

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe just call it beatmap-tag-picker instead?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i feel like this would make it too ambiguous whether it concerns mapper tags or user tags. not sure how those are generally named throughout the project

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

right. except the mapper tag is attached to beatmapset, not beatmap. and I think user tag is referred as beatmap tag everywhere

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do a two steps commit - one renaming the file, and another one updating the file. Otherwise the history won't get carried over to the new file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants