kdl-org / vscode-kdl Goto Github PK

If I under the spec correctly, I believe the whole thing of /-"comment ull" should be commented out instead of just until the space (since slashdot should be for the whole node / value).

Source

Can you please provide a license for this repo?

We have icons! I just don't know how to get them in as the extension icon. Help with this would be fantastic.

• Extension version: 1.3.1
• VSCode version: 1.72.0

If a raw string contains a " character, the syntax highlighting incorrectly considers that the end of the string, leading to strange and incorrect syntax highlighting. Example below.

VSCode recognizes +10 as a entity.name.tag but 10 as constant.numeric.integer.decimal.rust

This ultimately occurs because +10 is both a valid node name, and entry. Ideally +10 should be highlighted differently in the document +10 +10, but I don't thing this is achievable with regex's. But I think if +10 can only be a number or identifier, it's more likely to be a number.

I have literally no idea how to do this using the tm stuff. I would love some help on this.

I wrote a tree-sitter grammar for kdl here, it'd be cool to see it integrated into vscode for highlighting since it can provide much more info, as it is for neovim.

I'm using an open source build of VSCode called code-oss. This and most other OSS versions of VSCode use the OpenVSX plugin marketplace. It would be great if it was available there: https://open-vsx.org

Example text

command "twitter" "tw" url="https://twitter.com/" {
    match regexp="^@(?<username>[A-Za-z_]+)$" url="https://twitter.com/{username}" encoding="path"
    default url="https://twitter.com/search?q={}" encoding="query"
}

If I remove the = from the string, it looks fine:

KDL 2.0.0-draft.3 is now generally available (kdl-org/kdl#286), and with it, we've decided to encourage existing implementations to start working towards 2.0 support and send feedback and suggestions for anything you might run into, so I'm making this tracking issue. :)

P.S. We might want to just wait until #12 happens and that grammar is updated for 2.0.

KDL 1.0 is out! Let's make sure this extension is up to speed.

example text:

/-command "twitter" "tw" {
    rules {
        // profiles (format: @username)
        custom "https://twitter.com/{/username}" \
            regexp="^@(?P<username>[A-Za-z_]+)$"

        noargs "https://twitter.com"
        freeform "https://twitter.com/search?q={ARGS}"
    }

    tests {
        case "tw" "https://twitter.com"
        case "tw @sargunv" "https://twitter.com/sargunv"
        case "tw sargun vohra" "https://twitter.com/search?q=sargun%20vohra"
    }
}