@dchiquit I don't typically like to butt in on other people's features like this, but I needed to mess around with code to see if my idea would even work.
Here's a suggestion that I think simplifies things a bit. The one part of your PR that I was opposed to was the use of this inside the ActionKeys handler function, because it isn't clear how the function context gets set and I found it confusing. I know I did it that way initially, and that wasn't great.
Now, the actions computed prop adds a computed url to the action iff a urlfunc exists, and if that is found, the v-list-itemhref (and optionally, target) are used.
Let me know what you think. We don't have to actually merge this PR, just thought it'd be helpful to see.
@dchiquit I don't typically like to butt in on other people's features like this, but I needed to mess around with code to see if my idea would even work.
Here's a suggestion that I think simplifies things a bit. The one part of your PR that I was opposed to was the use of
this
inside theActionKeys
handler function, because it isn't clear how the function context gets set and I found it confusing. I know I did it that way initially, and that wasn't great.Now, the
actions
computed prop adds a computedurl
to the action iff aurlfunc
exists, and if that is found, thev-list-item
href
(and optionally,target
) are used.Let me know what you think. We don't have to actually merge this PR, just thought it'd be helpful to see.