Open jtbr opened 5 days ago
The recent changes introduce support for Bash scripting into the Tabby project. Enhancements include updating configuration files to recognize Bash language, adding a relevant parser dependency, defining function structures, and updating documentation to reflect the newfound support. This integration allows for better handling and parsing of Bash scripts within the Tabby ecosystem.
Files | Change Summary |
---|---|
crates/tabby-common/assets/languages.toml |
Updated to include top-level keywords specific to Bash scripting. |
crates/tabby-scheduler/Cargo.toml |
Added tree-sitter-bash dependency. |
crates/tabby-scheduler/queries/bash.scm |
Introduced function definition structure in a Scheme file. |
crates/tabby-scheduler/src/code/languages.rs |
Added configuration for the Bash language using tree-sitter-bash in the lazy static block. |
website/docs/programming-languages.md |
Updated documentation to reflect Bash support since version 0.14.0 . |
Beneath the stars, where scripts do splash,
Now supports the tongue they call Bash.
With keywords keen and functions clear,
Our code it reads without a sneer.
Documentation sings its name,
In Tabby’s heart, Bash finds its fame.
🐇✨
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
it seems the test if failing
Duplicate extension found: sh
Could you try fix it? maybe it's a configuratiohn mistake in config.toml
seems to be some issue with the tests.. not sure how any of that works...
Then it seems the tree-sitter-bash implementation is somewhat broken and caused the breakage?
Could be wrong, but I don't think it's the library. The test fails at:
code::intelligence::tests::test_create_source_file
It seems that some test suite does not know how to create a test file in the bash scripting language. I don't know anything about this test suite though.
support for bash shell scripting language
I think the only tag type applicable to scripts is function definitions; tree-sitter is all new to me so might want to have a look over that.
Also, while bash scripts commonly end in
.sh
, they often have no file extension, but are instead identified by the file beginning with#!/bin/bash
,#!/bin/sh
or similar (they are also normally marked as executable). Not sure if there is any way to support looking for these attributes instead of just the filename.Summary by CodeRabbit