tree-sitter-qmljs
QML grammar for the tree-sitter parsing library.
References
Pitfalls
Since grouped binding notation is syntactically ambiguous, it is parsed as an object definition.
// (ui_object_definition type_name: (identifier "Button") ...)
Button {
// (ui_object_definition type_name: (identifier "icon") ...)
icon { source: "foo.png"; color: "transparent" }
}
Building
Use the master branch, which contains all generated files.
$ git checkout master
$ npm install
$ cargo build --release
Hacking
Use the dev branch, but you'll first need to run npm install in the
master branch.
$ git checkout master
$ npm install
$ git checkout dev
Generate code and run tests:
$ make generate tests
Make sure example QML files can be parsed:
$ make fetch-examples parse-examples
1 maintainer
Metadata
1 maintainer
Release files for tree-sitter-qmljs 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| tree_sitter_qmljs-0.3.1.tar.gz | 440.1 kB | Without provenance | Details |
Release files / tree_sitter_qmljs-0.3.1.tar.gz
| Download URL | tree_sitter_qmljs-0.3.1.tar.gz |
|---|---|
| Size | 440.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8cf59d0a94fb4d593db2cfe5b66eb90e1accb98f47d10abe4b10ff78438716b0
|
|
BLAKE2b-256 checksum How to use checksums |
1b7a6299e4da0a02b6a792c28caaf03c128f42349a0c154cf77ab16fd5627ffc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.6
|
Security for tree-sitter-qmljs 0.3.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
