Skip to content

Conversation

@Dudemanguy
Copy link
Member

No description provided.

No need to have a switch here. It's not like the enum order should be
changed willy-nilly (although the next commit is going to do that).
@na-na-hi
Copy link
Contributor

There is no reason to add these when they can already be achieved with the index argument set to 0 (prepend) or playlist-pos (insert-prev).

@Dudemanguy
Copy link
Member Author

Shorthands. Of course you can already achieve these (and others) if you use insert-at.

@na-na-hi
Copy link
Contributor

These "shorthands" only add interface complexity that led to #16837. I think it is better to document the insert-at 0 and insert-at ${playlist-pos} usage examples instead.

@Dudemanguy
Copy link
Member Author

insert-prev looks less complex to me than insert-at ${playlist-pos}

@na-na-hi
Copy link
Contributor

I still think mention in documentation is enough. We should not add less generic interfaces when generic ones are available.

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