ivuorinen/tree-sitter-shellspec
1
0
Fork 0
mirror of https://github.com/ivuorinen/tree-sitter-shellspec.git synced 2026-01-26 11:43:59 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
5bc95f0bcdff69e5c18e1b905ef87985e136803f
tree-sitter-shellspec/.github/ISSUE_TEMPLATE/feature_request.md
Ismo Vuorinen c8ba576b4e feat: implement complete tree-sitter-shellspec grammar with comprehensive testing 
- Add full ShellSpec grammar extending tree-sitter-bash
- Support all ShellSpec constructs: Describe, Context, It, hooks, utilities
- Include Data block parsing with statements and argument styles
- Add 61 comprehensive test cases covering real-world patterns
- Implement optimized GitHub workflows with CI/CD automation
- Configure complete development tooling (linting, formatting, pre-commit)
- Add comprehensive documentation and contribution guidelines
- Optimize grammar conflicts to zero warnings
- Support editor integration for Neovim, VS Code, Emacs

Breaking Changes:
- Initial release, no previous API to break

BREAKING CHANGE: Initial implementation of tree-sitter-shellspec grammar

# Conflicts:
#	.github/workflows/codeql.yml
#	.github/workflows/pr-lint.yml
#	.pre-commit-config.yaml

# Conflicts:
#	.github/workflows/pr-lint.yml

# Conflicts:
#	.github/workflows/pr-lint.yml
2026-01-04 15:32:39 +02:00

1.0 KiB
Raw Blame History

name, about, title, labels, assignees
name about title labels assignees
Feature request Suggest a grammar enhancement or new feature for tree-sitter-shellspec [FEATURE] enhancement ivuorinen

Is your feature request related to a ShellSpec parsing issue? A clear description of what ShellSpec syntax is not currently supported. Ex. "Data blocks with :expand modifier are not parsed correctly"

ShellSpec syntax example Please provide an example of the ShellSpec syntax you'd like to see supported:

# Example ShellSpec code that should be supported

Describe the solution you'd like A clear description of how this syntax should be parsed or highlighted.

Current behavior How does the parser currently handle this syntax? (if at all)

Use case Why is this syntax important? How commonly is it used in ShellSpec tests?

Additional context

  • Link to ShellSpec documentation for this feature (if available)
  • Examples from real-world ShellSpec test suites
  • Any other context or screenshots about the feature request