WIP: Apply filter configuration to problem feature #228

Draft
Gabbar-v7 wants to merge 3 commits from Gabbar-v7/feat/config into master
Gabbar-v7 commented 2026-06-27 06:32:46 -05:00 (Migrated from github.com)

This pull request updates the way the "List" button on the Problems page filters problem status based on user configuration. The main change is to allow the button to pass the user's preferred status filter (such as "ac", "notac", or "todo") when listing problems. This required updating both the configuration template and the button's behavior.

User status filter integration:

  • Added a new status field to the leetcode.config template, allowing users to specify their preferred problem status filter (e.g., "ac", "notac", "todo", or nil).
  • Modified the "List" button in problems.lua so that when pressed, it calls cmd.problems with the user's configured status filter.
  • Included the leetcode.config module in problems.lua to access the user's status configuration.
This pull request updates the way the "List" button on the Problems page filters problem status based on user configuration. The main change is to allow the button to pass the user's preferred status filter (such as "ac", "notac", or "todo") when listing problems. This required updating both the configuration template and the button's behavior. **User status filter integration:** * Added a new `status` field to the `leetcode.config` template, allowing users to specify their preferred problem status filter (e.g., "ac", "notac", "todo", or `nil`). * Modified the "List" button in `problems.lua` so that when pressed, it calls `cmd.problems` with the user's configured status filter. * Included the `leetcode.config` module in `problems.lua` to access the user's status configuration.
Gabbar-v7 commented 2026-06-27 14:29:22 -05:00 (Migrated from github.com)

This is just a mock implementation. I can raise a proper production PR if you could guide me.

This is just a mock implementation. I can raise a proper production PR if you could guide me.
This pull request is marked as a work in progress.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin Gabbar-v7/feat/config:Gabbar-v7/feat/config
git switch Gabbar-v7/feat/config

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch master
git merge --no-ff Gabbar-v7/feat/config
git switch Gabbar-v7/feat/config
git rebase master
git switch master
git merge --ff-only Gabbar-v7/feat/config
git switch Gabbar-v7/feat/config
git rebase master
git switch master
git merge --no-ff Gabbar-v7/feat/config
git switch master
git merge --squash Gabbar-v7/feat/config
git switch master
git merge --ff-only Gabbar-v7/feat/config
git switch master
git merge Gabbar-v7/feat/config
git push origin master
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
arduinohatesme/leetcode.nvim!228
No description provided.