Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add leetcode.nvim to available plugins. #468

Closed
1 task done
Elias-Ainsworth opened this issue Nov 14, 2024 · 5 comments
Closed
1 task done

Add leetcode.nvim to available plugins. #468

Elias-Ainsworth opened this issue Nov 14, 2024 · 5 comments

Comments

@Elias-Ainsworth
Copy link

⚠️ Please verify that this feature request has NOT been suggested before.

  • I checked and didn't find a similar feature request

🏷️ Feature Type

New Addon

🔖 Feature description

Implementation of the leetcode.nvim plugin...cuz leetcode.

✔️ Solution

In the same way that precognition, and alpha are implemented an implementation of this would be nice (also a way to declare the graphql cookie via an exposed option (that one could use sops to hide) would be nice).

❓ Alternatives

No response

📝 Additional Context

No response

@NotAShelf
Copy link
Owner

As the release of 0.7 is approach, I'm looking to reduce the number of new plugins before we merge into the main branch and continue there. I might implement this after 0.7, but since I don't use leetcode and would not be able to maintain or test a plugin for something I don't use, I think this is better submitted as a pull request.

Either way, I'll see what can be done after 0.7 is merged.

@ArmandoCIII
Copy link
Contributor

ArmandoCIII commented Feb 10, 2025

Hey @NotAShelf,
Working on this one now. Do you have a preferred plugins directory? I was considering making one called "competitive-programming" inspired by awesome-neovim category nomenclature. Let me know what you think. Thanks.

@NotAShelf
Copy link
Owner

I would probably have it under utility, but if there are other useful plugins for comp. programming that you think we may add in the future, then a new category is suitable.

@ArmandoCIII
Copy link
Contributor

In the short term, I do not think so. I will put it under utility and, if anything, can be refactored in the future. Thank you for your quick response.

@ArmandoCIII
Copy link
Contributor

Closed with #636.

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

No branches or pull requests

3 participants