support virtual variable value

.editorconfig

@@ -6,3 +6,6 @@ indent_style = space
 indent_size = 2
 charset = utf-8
 
+[Makefile]
+indent_style = tab
+

.github/workflows/conform-docs.yml

@@ -0,0 +1,21 @@
+---
+name: Conform Docs
+
+on:
+  pull_request:
+    paths:
+      - 'docs/**/*.md'
+    branches:
+      - main
+
+jobs:
+  lint:
+    name: Lint Docs
+    runs-on: ubuntu-latest
+    container:
+      image: ghcr.io/mistweaverco/kulala-nvim-testrunner:latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Run linter
+        run: ./scripts/lint.sh check-docs

.github/workflows/tests.yml

@@ -1,31 +1,68 @@
 ---
-name: Test
+name: Tests
 
 on:
   pull_request:
+    paths:
+      - '**/*.lua'
     branches:
       - main
 
 jobs:
-  tests:
-    name: Tests
-    runs-on: ${{ matrix.os }}
-    strategy:
-      fail-fast: false
-      matrix:
-        include:
-          - os: ubuntu-latest
-            container-image: ghcr.io/mistweaverco/kulala-nvim-testrunner:latest
+  test-linux:
+    name: Test Code on Linux
+    runs-on: ubuntu-latest
     container:
-      image: ${{ matrix.container-image }}
+      image: ghcr.io/mistweaverco/kulala-nvim-testrunner:latest
     steps:
       - uses: actions/checkout@v4
       - name: Restore cache
         uses: actions/cache@v4
         with:
           path: |
             .tests
-          key: ${{ runner.os }}-${{ matrix.container-image }}
-
+          key: ${{ runner.os }}-tests
       - name: Run tests
         run: ./scripts/tests.sh run
+  lint:
+    name: Lint Code
+    runs-on: ubuntu-latest
+    container:
+      image: ghcr.io/mistweaverco/kulala-nvim-testrunner:latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Run linter
+        run: ./scripts/lint.sh check-code
+  test-windows:
+    name: Test Code on Windows
+    runs-on: windows-latest
+    if: ${{ github.event.label.name == 'needs-windows-test' }}
+    steps:
+      - uses: actions/checkout@v4
+      - name: Restore cache
+        id: cache-deps
+        uses: actions/cache@v4
+        with:
+          path: |
+            .tests
+            ~\scoop
+            ~\AppData\Roaming\LJ4W
+            ~\AppData\Roaming\luarocks
+          key: ${{ runner.os }}-tests
+      - name: Check if cache hit
+        if: steps.cache-deps.outputs.cache-hit == 'true'
+        run: echo "GH_CACHE_HIT=true" >> $Env:GITHUB_ENV
+      - name: Install dependencies
+        run: ./scripts/install-ci-test-requirements.ps1
+      - name: Save cache
+        uses: actions/cache/save@v4
+        with:
+          path: |
+            .tests
+            ~\scoop
+            ~\AppData\Roaming\LJ4W
+            ~\AppData\Roaming\luarocks
+          key: ${{ runner.os }}-tests
+      - name: Run tests
+        run: ./scripts/tests.ps1

.gitignore

@@ -1,7 +1,9 @@
 node_modules
 .env
 http-client.env.json
+!/schemas/http-client.env.json
 *.http
 *graphql-schema.json
 /http-examples
 .tests
+.nvim

CODEOWNERS

@@ -0,0 +1 @@
+* @gorillamoe @Grueslayer

CODE_OF_CONDUCT.md

@@ -0,0 +1,85 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to make participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community includes using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting an individual maintainer on:
+
+### GitHub
+
+- @gorillamoe
+
+> (at `GitHub username` + `@github.com`).
+
+### Discord
+
+- gorillamoe
+
+All complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [https://contributor-covenant.org/version/1/4][version]
+
+[homepage]: https://contributor-covenant.org
+[version]: https://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,89 @@
+# Contributing to Kulala
+
+Thanks for checking out Kulala!
+We're excited to hear and learn from you.
+
+We've put together the following guidelines to
+help you figure out where you can best be helpful.
+
+## Table of Contents
+
+0. [Types of contributions we're looking for](#types-of-contributions-were-looking-for)
+0. [Ground rules & expectations](#ground-rules--expectations)
+0. [How to contribute](#how-to-contribute)
+0. [Style guide](#style-guide)
+  1. [Documentation](#documentation)
+  2. [Code](#code)
+0. [Setting up your environment](#setting-up-your-environment)
+0. [Community](#community)
+
+## Types of contributions we're looking for
+
+There are many ways you can directly contribute to Kulala:
+
+- Feature requests
+- Bug reports
+- Code contributions
+- Writing or editing documentation
+
+## Ground rules & expectations
+
+Before we get started,
+here are a few things we expect from you (and that you should expect from others):
+
+- Be kind and thoughtful in your conversations around this project.
+  We all come from different backgrounds and projects,
+  which means we likely have different perspectives on "how open source is done."
+  Try to listen to others rather than convince them that your way is correct.
+- Kulala is released with a [Contributor Code of Conduct](./CODE_OF_CONDUCT.md).
+  By participating in this project, you agree to abide by its terms.
+- Please ensure that your contribution passes all tests if you open a pull request.
+  If there are test failures, you will need to address them before we can merge your contribution.
+- When adding content, please consider if it is widely valuable.
+  Please don't add references or links to things you or your employer have created,
+  as others will do so if they appreciate it.
+
+## How to contribute
+
+If you'd like to contribute,
+start by searching through the [pull requests](https://github.com/mistweaverco/kulala.nvim/pulls) to
+see whether someone else has raised a similar idea or question.
+
+If you don't see your idea listed, and you think it fits into the goals of this guide, open a pull request.
+
+## Style guide
+
+### Documentation
+
+If you're writing documentation,
+see the [style guide](./docs/.vale/styles) (which uses [vale](https://vale.sh)) to
+help your prose match the rest of the documentation.
+
+### Code
+
+When writing code,
+please follow these configurations:
+
+- [stylua](./stylua.toml)
+- [luacheck](./.luacheckrc)
+- [EditorConfig](./.editorconfig)
+- [yaml-lint](./.yamllint.yaml)
+
+Most of them are automatically checked by the CI,
+so you don't need to worry about them.
+
+## Community
+
+Discussions about the Kulala take place on:
+
+- This repository's [Issues](https://github.com/mistweaverco/kulala.nvim/issues) and
+  [Pull Requests](https://github.com/mistweaverco/kulala.nvim/pulls) sections
+- The [Kulala Discord server](https://discord.gg/QyVQmfY4Rt)
+
+Anybody is welcome to join these conversations.
+
+Wherever possible,
+do not take these conversations to private channels,
+including contacting the maintainers directly.
+
+Keeping communication public means everybody can benefit and learn from the conversation.

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2024 mistweaver.co
+Copyright (c) 2024+ mistweaverco
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

Makefile

@@ -1,2 +1,13 @@
 version:
 	./scripts/set-version.sh $(VERSION)
+tag:
+	./scripts/tag.sh
+release:
+	./scripts/tag.sh
+docker-build:
+	if [ "$(OS)" != "linux" ] || [ "$(OS)" != "windows" ]; then (echo "OS must be either linux or windows"; exit 1); fi
+	docker build -t ghcr.io/mistweaverco/kulala-nvim-$(OS)-testrunner:latest tests/_dockerfiles/$(OS)
+docker-push:
+	if [ "$(OS)" != "linux" ] || [ "$(OS)" != "windows" ]; then (echo "OS must be either linux or windows"; exit 1); fi
+	docker push ghcr.io/mistweaverco/kulala-nvim-$(OS)-testrunner:latest
+

README.md

@@ -51,7 +51,7 @@ See [configuration options](https://kulala.mwco.app/docs/getting-started/configu
 
 For getting this project started.
 
-This project was heaviliy inspired by the idea of having a REST client in Neovim.
+This project was heavily inspired by the idea of having a REST client in Neovim.
 
 The actual state of [rest.nvim](https://github.com/rest-nvim/rest.nvim)
 as archived kicked off the development of kulala.nvim.

docs/.vale/styles/18F/Abbreviations.yml

@@ -0,0 +1,15 @@
+---
+extends: substitution
+message: "Use '%s' instead of '%s'."
+link: https://content-guide.18f.gov/specific-words-and-phrases/
+ignorecase: false
+level: error
+nonword: true
+swap:
+  '\beg\b': e.g.,
+  '\bie\b': i.e.,
+  'e\.g\.(?:[^,]|$)': e.g.,
+  'i\.e\.(?:[^,]|$)': i.e.,
+  '(?i)\d{1,2} ?[ap]m': a.m. or p.m.
+  'D\.C\.': DC
+  '\bUSA?\b': U.S.

docs/.vale/styles/18F/Ages.yml

@@ -0,0 +1,7 @@
+---
+extends: existence
+message: Avoid hyphens in ages unless it clarifies the text.
+link: https://content-guide.18f.gov/specific-words-and-phrases/
+level: warning
+tokens:
+  - '\d{1,3}-year-old'

docs/.vale/styles/18F/Brands.yml

@@ -0,0 +1,22 @@
+---
+extends: substitution
+message: "Use '%s' instead of '%s'."
+link: https://content-guide.18f.gov/trademarks-and-brands/
+level: warning
+ignorecase: true
+swap:
+  Band-Aid: bandage
+  Bubble Wrap: packaging bubbles
+  Chapstick: lip balm
+  Crayola: crayons
+  Dumpster: waste container
+  Hi-Liter: highlighting marker
+  iPod: MP3 player
+  Kleenex: tissue
+  Plexiglas: plastic glass
+  Post-it note: adhesive note
+  Q-Tips: cotton swabs
+  Scotch tape: transparent tape
+  Styrofoam: plastic foam
+  Taser: stun gun
+  Xerox: photocopy