Conversation
…& tested in prolog-and-literals.test
# Conflicts: # core/src/subject/SubjectEntity.ts # tests/js/tests/prolog-and-literals.test.ts
…riptions” to unflake
…ry between operations” to unflake
lucksus
previously approved these changes
Mar 18, 2025
lucksus
approved these changes
Mar 19, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Enhanced SubjectEntity Query System
This PR introduces a new, more powerful query system for SubjectEntity that enables complex queries with a fluent interface and real-time subscriptions to query results.
Key Features
Real-time Query Subscriptions: Subscribe to query results and receive updates when matching instances change
Huge for a much more performant implementation of our hooks! - coming next
Fluent Interface: Chain-able query building for better readability
Example usage
Implementation Details
The new query system works by:
This replaces the previous approach of fetching instances and their data separately, resulting in better performance and enabling more complex queries.