1be6047c8a
* feat(tracker): field-prefixed search, inline filter chips and zero-hit empty state Adds SearchInputAdvanced (field:value prefixes routed to Elasticsearch query_string), match highlighting, inline filter chips with overflow popover, a reusable zero-hit empty state in view-resources, and search-scope/highlight view options for List and Kanban. Signed-off-by: Michael Uray <michaeluray@users.noreply.github.com> * refactor(tracker-search): address review follow-ups on search/filter rework Shared, non-storage-specific field list, test-folder conventions, locale coverage, single regex source and an owner-token gate for the result count. - core: add shared `fullTextSearchFields` constant next to FullTextSearchContext as the single source of truth for the full-text fields exposed to `field:value` targeting. The client encoder derives ES_NATIVE_FIELDS from it and the elastic adapter derives KNOWN_FIELD_RE from it, replacing the two "KEEP IN SYNC" copies. Per-field boost weights stay a local adapter detail. - tests: move the five co-located tests into each package's existing test folder convention (ui `__test__`, view-resources `__tests__`) and fix the relative imports. - i18n: translate the new tracker search/filter strings in the remaining locales (zh, ja, ko, cs, es, fr, it, pt, pt-br, tr), reusing each file's existing terminology; ICU placeholders left unchanged. - encoder: hoist the reserved-character class into one constant and build two RegExp instances from it (non-global for `.test()`, global for `.replace()`) to avoid the shared-lastIndex trap. - view-resources: guard `resultIssueCountStore` writes with an owner-token gate so a superseded viewlet can no longer clobber the active viewlet's count; List/KanbanView claim and release, IssuesView resets through the current owner. Assumes a single active IssuesView surface. - view-resources: make result-count reporting opt-in via a new `reportResultCount` prop on List (default true). Embedded, non-primary List instances (sub-issues / related issues in the issue edit panel, routed through SubIssueList) pass false and never claim the owner token, so opening and closing an issue can no longer strand the primary Issues viewlet with a dead token — the zero-hit SearchEmptyState card renders again afterwards. Add a regression test covering the opted-out embedded consumer. - elastic: escape every regex metacharacter (not just `.`) when building KNOWN_FIELD_RE from `fullTextSearchFields`, so a future field name carrying another metacharacter cannot silently corrupt the alternation. Behaviour for the current fields is unchanged. Signed-off-by: Michael Uray <michaeluray@users.noreply.github.com> * refactor(tracker-search): centralize regex escaping and lock down result-count store - Share escapeRegExp from @hcengineering/core so the client encoder and the server elastic adapter escape the fulltext field list identically, not just dots on the client. - Export resultIssueCountStore as a read-only Readable; the owner-token gate functions (setResultCount / resetResultCount / releaseResultCountOwner) are now the only write path. Signed-off-by: Michael Uray <michaeluray@users.noreply.github.com> --------- Signed-off-by: Michael Uray <michaeluray@users.noreply.github.com> Co-authored-by: Michael Uray <michaeluray@users.noreply.github.com> Co-authored-by: Artyom Savchenko <armisav@gmail.com>
Huly Core
⭐️ Your star shines on us. Star us on GitHub!
About
Huly Core is a collection of core packages extracted from the Huly Platform. This repository contains fundamental building blocks and libraries that power the Huly ecosystem, including core data models, client libraries, text processing engines, and platform utilities.
These packages are designed to be reusable, modular, and framework-agnostic, making them suitable for building custom applications on top of the Huly Platform or integrating Huly functionality into existing projects.
Packages
This repository includes the following core packages:
Core Packages
- @hcengineering/core - Core data models, types, and fundamental platform abstractions
- @hcengineering/platform - Platform runtime, plugin system, and dependency injection
- @hcengineering/model - Data model definitions and schema management
Client Libraries
- @hcengineering/client - Client-side data access and synchronization layer
- @hcengineering/client-resources - Shared client resources and utilities
- @hcengineering/api-client - API client for programmatic access to Huly Platform (WebSocket and REST)
- @hcengineering/account-client - Account management client
- @hcengineering/collaborator-client - Real-time collaboration client
- @hcengineering/hulylake-client - HulyLake data warehouse client
- @hcengineering/analytics - Analytics and tracking
- @hcengineering/analytics-service - Analytics service implementation
Text Processing
- @hcengineering/text - High-level text processing utilities
- @hcengineering/text-core - Core text processing engine
- @hcengineering/text-html - HTML text rendering and parsing
- @hcengineering/text-markdown - Markdown support
- @hcengineering/text-ydoc - Yjs document integration for collaborative editing
Utilities
- @hcengineering/query - Query language and execution engine
- @hcengineering/storage - Storage abstractions and implementations
- @hcengineering/rank - Ranking and ordering utilities
- @hcengineering/retry - Retry logic and resilience patterns
- @hcengineering/rpc - RPC communication layer
- @hcengineering/token - Token management and authentication utilities
Pre-requisites
Before proceeding, ensure that your system meets the following requirements:
Installation
You need Microsoft's rush to install the application.
- Install Rush globally using the command:
npm install -g @microsoft/rush
- Navigate to the repository root and run the following commands:
rush install
rush build
Build
To build all packages:
rush build
To rebuild (ignoring cache):
rush rebuild
Build & Watch
For development purposes, rush build:watch action could be used:
rush build:watch
It includes build and validate phases in watch mode.
Update project structure
If the project's structure is updated, it may be necessary to relink and rebuild the projects:
rush update
rush build
Troubleshooting
If a build fails, but the code is correct, try to delete the build cache and retry:
rm -rf common/temp/build-cache
rush rebuild
Tests
To execute all tests:
rush test
For individual test execution inside a package directory:
rushx test
Package Publishing
To bump a package version:
node ./common/scripts/bump.js -p projectName
API Client Usage
If you want to interact with Huly programmatically, check out the API Client documentation. The API client provides a typed interface for all Huly operations and can be used to build integrations and custom applications.
You can find API usage examples in the Huly examples repository.
Related Projects
- Huly Platform - The main Huly Platform repository
- Huly Self-Host - Self-hosting solution for Huly
- Huly Examples - API usage examples
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
Licensed under the EPL-2.0 license.
Additional Links
© 2025 Hardcore Engineering Inc.