feat: Remove <Leader>f mapping from community plugin

[shivanthzen]

📑 Description

ℹ Additional Information

[github-actions[bot]]

Review Checklist

Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:

Proper conventional commit scoping:

• If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin

• If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error

• [x] Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above

• [x] README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url)

• [x] Entry returns a single plugin spec with the new plugin as the only top level spec (not applicable for recipes or packs).

• [x] Proper usage of opts table rather than setting things up with the config function.

• [x] Proper usage of specs table for all specs that are not dependencies of a given plugin (not applicable for recipes or packs).

[azdanov]

What is the reason to remove it? It conflicts with an existing mapping?

[ButterSus]

.

<leader>f is prefix for all picker actions. It actually overlaps. Wouldn't it be better to remap it? <leader>ue for example. <leader>ue and <leader>uE are not mentioned in astrocommunity/

[Uzaaft]

Any updates on this? @shivanthzen

[shivanthzen]

@Uzaaft

[Uzaaft]

Answer the question that azdanov asked @shivanthzen before pinging me...

[shivanthzen]

<leader>f is prefix for all picker actions. It actually overlaps. Wouldn't it be better to remap it? <leader>ue for example. <leader>ue and <leader>uE are not mentioned in astrocommunity/

Already answered here

[azdanov]

Looks good. Thanks! @Uzaaft what do you think? Seems like a breaking change, so I updated the title accordingly.