update tree-sitter-dart to the upstream, maintained version #405

Closed
HannesGitH wants to merge 1 commit from HannesGitH/mergiraf:main into main
First-time contributor

unfortunately the used tree-sitter-dart crate is a unmaintained, archived fork.

It doesnt understand a large portion of newer dart syntax, like e.g. Records

this pr introduces a much more up-to-date fork

unfortunately the used tree-sitter-dart crate is a unmaintained, archived fork. It doesnt understand a large portion of newer dart syntax, like e.g. Records this pr introduces a much more up-to-date fork
update tree-sitter-dart to the upstream, maintained version
Some checks failed
/ test (pull_request) Failing after 1m44s
cfb6b09b59
Owner

One problem with this is that we wouldn't be able to publish a new version of Mergiraf to Crates.io with a dependency specified like this (with a bare git revision). But I guess users of Dart would be able to at least build Mergiraf from source off of this branch in order to have access to the better-maintained repo

One problem with this is that we wouldn't be able to publish a new version of Mergiraf to Crates.io with a dependency specified like this (with a bare git revision). But I guess users of Dart would be able to at least build Mergiraf from source off of this branch in order to have access to the better-maintained repo
Owner

Oh and the test failure looks interesting? Not sure whether it's a bug in Mergiraf or in this new grammar

Oh and the test failure looks interesting? Not sure whether it's a bug in Mergiraf or in this new grammar
Owner

Totally forgot – welcome and thanks for the PR!

Totally forgot – welcome and thanks for the PR!
Author
First-time contributor

@ada4a wrote in #405 (comment):

Totally forgot – welcome and thanks for the PR!

hehe thanks!

Oh and the test failure looks interesting? Not sure whether it's a bug in Mergiraf or in this new grammar

yep, didnt have the time to dig deeper tho, had to overrideAttrs {doCheck = false;} in my config but at least it works for now, i'll keep you posted

@ada4a wrote in https://codeberg.org/mergiraf/mergiraf/pulls/405#issuecomment-4802778: > Totally forgot – welcome and thanks for the PR! hehe thanks! > Oh and the test failure looks interesting? Not sure whether it's a bug in Mergiraf or in this new grammar yep, didnt have the time to dig deeper tho, had to `overrideAttrs {doCheck = false;}` in my config but at least it works for now, i'll keep you posted
Owner

I'm idly considering forking this grammar into the grammar-orchard to get this unblocked. If anyone wants to do it, I'd be happy to support.

I'm idly considering forking this grammar into the [grammar-orchard](https://codeberg.org/grammar-orchard) to get this unblocked. If anyone wants to do it, I'd be happy to support.
Owner

Closing in favour of #557.

Closing in favour of #557.
wetneb closed this pull request 2025-08-01 23:20:21 +02:00
Some checks failed
/ test (pull_request) Failing after 1m44s

Pull request closed

Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: mergiraf/mergiraf#405
No description provided.