feat(v25)!: New version release

- Completely rewritten `markview.nvim`
- Adds typst support
- Better rendering logic
- Performance optimizations.
- More customization

And more!

Closes: #177

BEGIN_COMMIT_OVERRIDE
refactor(renderer): More optimized renderer that redraws previews only
when necessary
refactor(parser): Improved various parsing logic
refactor(core): Various load time lags has been resolved
refactor(dynamic_highlights): Color merging is now done via `Lab`
instead of `RGB`
refactor(renderer_markdown): Better renderer for Tables
refactor(parser_inline): More link support for inline markdown
feat(core): Added typst support
refactor(parser_latex): Improve detection of inline & block equations
refactor(renderer_latex): Better latex rendering
refactor(spec)!: Complete redesign of the configuration table
feat(spec)!: Dynamic configuration support
refactor(parser_markdown): Added support for alternate code block styles
refactor: Added more icon support
refactor: Added more filetype support for code blocks
feat(renderer_markdown): Added diff support to code blocks
feat(spec): Added pattern based config support for various items
refactor(renderer_yaml): Improved the renderer for YAML properties
fix: Various QOL fixes
refactor(core): Complete overhaul to the `:Markview` command
refactor(extras)!: Completely changed how extra modules are used via
commands
feat(extras): Added `interactive mode` to the checkbox switcher
feat(core)!: Added ability to make hybrid mode only affect certain items
feat(core)!: Added linewise hybrid mode
feat(renderer_html)!: Complete overhaul to hoe different HTML elements
are rendered
refactor(presets): More presets
refactor(doc): Added vimdoc documentation
refactor(renderer_inline): Added more entity support
chore: Added some testing files
feat(core): Added ability to see traces & export traces
refactor(links): Better link opener
END_COMMIT_OVERRIDE

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,55 +1,91 @@
 name: Bug report
-description: Report a bug in markview
-title: '🐞 Bug: '
+description: "Report a bug in markview."
+title: "🐞 Bug: "
 labels: [ "bug" ]
-assignees:
-  - OXY2DEV
 body:
   - type: checkboxes
-    id: issue-conditions
+    id: branch
     attributes:
-      label: 'Before reporting:'
-      description: |
-        These are **requirements** and failing to fulfill them will result the issue to be closed.
+      labels: "🤖 Which branch are you using?"
       options:
-        - label: Ensure that the issue is reproducable on the main branch.
-          required: true
-        - label: Ensure that there isn't an issue on this(either open or closed).
-          required: true
+        - label: "dev"
+        - label: "main"
+
   - type: textarea
-    id: issue-desc
+    id: desc
     attributes:
-      label: 'Problem:'
-      description: |
-        Describe the current behavior(images, gif, videos & logs) may be attached.
-      placeholder: A description of the issue...
+      label: "📜 Issue description:"
+      description: "Describe the issue in a *clear* and *concise* way. You should also attach `images`/`gifs` if it's a visual bug."
+      placeholder: "Fenced code blocks don't render when..."
     validations:
       required: true
+
   - type: textarea
-    id: issue-repro
+    id: repro
     attributes:
-      label: 'Steps to reproduce the issue:'
+      label: "📑 Reproduction steps:"
+      description: "Give step by step instructions on how to recreate the issue using the `minimal init`."
+      placeholder: "1. Open Neovim."
+    validations:
+      required: true
+
+  - type: textarea
+    id: minit
+    attributes:
+      label: "💻 Minimal init:"
       description: |
-        *Things to check before opening an issue:*
-        - Ensure that you don't have other `markdown` plugins enabled(unless it's a comparability issue with that plugin).
-        - Ensure that you are using the **latest version** of the plugin.
-        - Ensure that your `Neovim` version is **>=0.10**.
-        - Ensure that you have the correct `tree-sitter` parsers
-        installed(markdown, markdown_inline & html).
-      placeholder: nvim
+        The minimal config file to reproduce the issue.
+
+        Put this in a file(e.g. `minit.lua`) and do `nvim -u minit.lua` to run it.
+      placeholder: |
+        vim.env.LAZY_STDPATH = ".repro"
+        load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()
+
+        require("lazy.minit").repro({
+            spec = {
+                {
+                    "nvim-treesitter/nvim-treesitter",
+                    build = ":TSUpdate",
+
+                    ensure_installed = { "html", "latex", "markdown", "markdown_inline", "typst", "yaml" }
+                },
+                {
+                    "OXY2DEV/markview.nvim",
+                    -- branch = "dev",
+                    lazy = false
+                }
+            },
+        });
     validations:
       required: true
+
   - type: textarea
-    id: issue-expected
+    id: repro
     attributes:
-      label: 'Expected behavior:'
-      description: Describe what should've happened.
-      placeholder: Markview should've...
+      label: "📜 Logs:"
+      description: |
+        After Reproducing the bug, run `:Markview traceExport`. You will see a new file `trace.log` has been created in your current directory.
+
+        Copy it's contents here.
+      placeholder: "Logs..."
+    validations:
+      required: true
+
   - type: input
-    id: issue-nvim_v
+    id: nvim-ver
+    attributes:
+      label: "Neovim version:"
+      description: "Neovim version."
+      placeholder: "nvim -v"
+    validations:
+      required: true
+
+  - type: textarea
+    id: minit
     attributes:
-      label: 'Neovim version:'
-      description: Neovim version.
-      placeholder: nvim -v
+      label: "✅ Expected behavior:"
+      description: "The expected behavior."
+      placeholder: "Markview should..."
     validations:
       required: true
+

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,28 +1,32 @@
 name: Feature Request
-description: Request a new feature in markview
-title: '✨ Feature: '
+description: "Request a new feature."
+title: "✨ Feature: "
 labels: [ "enhancement" ]
-assignees:
-  - OXY2DEV
 body:
-  - type: checkboxes
-    id: feat-type
-    attributes:
-      label: 'The nature of the feature:'
-      description: |
-        Select one or more options that describes this feature.
-      options:
-        - label: Parser(syntax, conceal etc. related)
-        - label: Renderer(style, options etc. related)
-        - label: Support(plugin support, language support etc. related)
-        - label: Other
   - type: textarea
     id: feat-desc
     attributes:
-      label: 'Description:'
-      description: |
-        Describe the feature(images, videos, referances are welcome).
-      placeholder: A description of the feature...
+      label: "🔖 Feature description:"
+      description: "Briefly describe what the feature does."
+      placeholder: "We should have a way to..."
     validations:
       required: true
 
+  - type: textarea
+    id: solutions
+    attributes:
+      label: "📂 Possible solutions:"
+      description: "Describe the solutions you have thought of on how to add this."
+      placeholder: "We should probably add..."
+    validations:
+      required: false
+
+  - type: textarea
+    id: feat-ref
+    attributes:
+      label: "🧾 Feature reference:"
+      description: "Reference features similar to what you wanted(if applicable)."
+      placeholder: "This feature is available in..."
+    validations:
+      required: false
+

.github/workflows/stale.yml

@@ -6,7 +6,6 @@ on:
 
 jobs:
   stale:
-
     runs-on: ubuntu-latest
     permissions:
       issues: write
@@ -16,8 +15,17 @@ jobs:
     - uses: actions/stale@v5
       with:
         repo-token: ${{ secrets.GITHUB_TOKEN }}
-        stale-issue-message: '🤖 Bot: **Issue** has not seen activity in **30** days and will therefore be marked as stale. It will be closed in 7 days if no further response is found.'
-        stale-pr-message: '🤖 Bot: **PR** has not seen activity in **30** days and will therefore be marked as stale. It will be closed in 7 days if no further response is found.'
+        days-before-stale: 30
+        days-before-close: 7
+        exempt-issue-labels: dev,important
+
+        stale-issue-message: |
+          🤖 Bot: There has been no recent activity in this issue. Without new activity this issue will be closed in **7** days.
+        stale-pr-message: |
+          🤖 Bot: There has been no recent activity in this PR. Without new activity this PR will be closed in **7** days.
+
         stale-issue-label: 'no-issue-activity'
         stale-pr-label: 'no-pr-activity'
-        days-before-stale: 30
+
+        close-issue-label: 'no-issue-activity'
+        close-pr-label: 'no-pr-activity'