Conversation
* Add clang and clang-tidy
|
Tested against HyDE scripts compatibility. Fixed issue: Source paths with inline comments were not parsed correctly, causing the Tested all variables from HyDE $ hydequery ~/.config/hypr/hyprland.conf -s \
-Q '$GTK_THEME' \
-Q '$ICON_THEME' \
-Q '$CURSOR_THEME' \
-Q '$CURSOR_SIZE' \
-Q '$COLOR_SCHEME'
Wallbash-Gtk
Tela-circle-dracula
Bibata-Modern-Ice
24
prefer-darkExport formats work correctly: env format (for shell scripts): $ hydequery ... --export env
GTK_THEME="Wallbash-Gtk"
ICON_THEME="Tela-circle-dracula"Nested config values: $ hydequery ~/.config/hypr/hyprland.conf -s \
-Q 'general:border_size' -Q 'decoration:rounding'
2
3All HyDE theme variables are accessible through the main hyprland.conf with |
Added comprehensive tests with real HyDE config examples: - export.rs: 100% coverage - source.rs: 96% coverage - value.rs: 98% coverage - query.rs: 97% coverage - schema.rs: 96% coverage - path.rs: 96% coverage Integration tests cover real HyDE scenarios: - Theme variables (GTK_THEME, ICON_THEME, CURSOR_SIZE) - General settings (gaps, border_size, rounding) - Source directive chaining - Decoration and animation configs
Separated Args::parse() from main logic to enable comprehensive testing. Coverage improved from 74% to 86%: - app.rs: 93% (was 44%) - Core business logic fully covered Added 30+ tests for run_with_args covering: - Theme variables (GTK_THEME, ICON_THEME, CURSOR_SIZE) - General/decoration settings - Source directive following - Type and regex filters - Error cases (missing vars, invalid paths) - Export formats (json, env, plain)
…ages - Make config_file optional to allow --fetch-schema standalone - Add validation_error for clear user feedback - Fix error display to show actual message instead of error kind - Update help and man page to reflect new CLI patterns
- Fix ASCII art to spell HYDEQUERY instead of HYPRQUE - Add filters.rs and defaults.rs to architecture section - Add --get-defaults example - Clarify that -Q is not required for all operations
- Add benchmarks for query parsing (simple, typed, regex) - Add benchmarks for file I/O operations - Add benchmarks for full query execution - Add lib.rs to expose modules for benchmarking - Add Clone derive to Args for benchmark iterations - Fix doctests in fetch.rs
|
- Add cliff.toml configuration for conventional commits - Add changelog CI job that runs on push to main - Generate initial CHANGELOG.md from commit history - Configure commit message parsing for features, fixes, docs, etc.
- Configure weekly dependency checks for Cargo and GitHub Actions - Group all minor/patch updates into single PRs by ecosystem - Auto-merge and auto-approve minor/patch updates after CI passes - Use squash merge for clean history
|
@kRHYME7, i'm think i'm done) let's check this stuff! i'll add benchmark section in readme later |
|
@RAprogramm can you name the binary |
|
@kRHYME7 works good? |
So how it could be? |
|
hyq for the binary executable name. hyprquery because it can be a stand alone tool to parse hypr configs. |
|
Got you! |
|
@RAprogramm would you mind pushing this against an empty edit: jsut for the sake of diffing rs files against rs file! |
@prime-run dev branch created, bro! yes, it's a good practice to protect main/master branch |
|
@kRHYME7 , done, renamed to |
|
cool, I clean up dev branch. would be great if you deal with conflicts. then we merge and take from there. P.S maybe keep that warning I added on top of the README.md ?! edit: let me squash everything in dev too. |
|
@RAprogramm Alright, we have a clean history under |
|
@RAprogramm I did the cherry picking and pushed to hdev branch Would be great if you could confirm your commit history there. |
4 participants
Closes #2