feat(bars-and-lines): add plugins wakastat.nvim

[fiqryq]

📑 Description

Add plugins wakastat.nvim for display WakaTime coding stats in your Neovim statusline — supports daily, weekly, or monthly views, custom formatting, and async updates.

ℹ Additional Information

Usage

return {
  {
    "fiqryq/wakastat.nvim",
    event = "VeryLazy",
    cmd = { "WakastatRefresh", "WakastatStatus" },
    opts = {
      args = { "--today" },                  -- or "--week", "--month"
      format = "Today Coding Time: %s",      -- %s replaced with time
      update_interval = 300,                 -- seconds between updates
      enable_timer = true,
    },
    config = function(_, opts)
      require("wakastat").setup(opts)
    end,

    specs = {
      {
        "rebelot/heirline.nvim",
        optional = true,
        opts = function(_, opts)
          opts.statusline = opts.statusline or {}
          table.insert(opts.statusline, 5, {  -- insert at position 5
            provider = function()
              return " " .. require("wakastat").status() .. " "
            end,
            hl = "Wakastat",
            update = { "User", pattern = "WakastatUpdated" },
          })
        end,
      },
    },
  },
}

[github-actions]

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

• 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

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

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

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

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

[Uzaaft]

Based on your docs @fiqryq this seems incomplete.

[fiqryq]

hi @Uzaaft i already update the spec for plugins.

[Uzaaft]

The insert at position 5 stuff seems jank. But shipping this for now.