v3.0.0.b1 #424
Merged
v3.0.0.b1 #424
Conversation
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
…Base. Small fixes for various mutations.
…s and extract floaters.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
…gDocumentControls, FloatingDocumentInput, FloatingExtractPanel, FloatingSummaryPreview, and UnifiedKnowledgeLayer.
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
…fix some legitimately broken parsing logic for dates. Removed superfluous frontend test actions (these tests run as part of full frontend component and unit tests.
…low. Added better indicators to user how to create labels for annotating. Overhauled permissioning docs. Tweaked and improved documentation on frontend labeling process.
This was
linked to
issues
Aug 18, 2025
… Further cleaned and updated docs.
…dLabelSelector to provide clear visual indication it's disabled in read_only mode
…rting this anyway.
… analyzers, improved logging for analysis processes, and added checks for unsynced analyzers. Updated frontend components for better annotation controls and refined GraphQL queries for document annotations. Updated dependencies and removed unused files.
This was
linked to
issues
Aug 22, 2025
…cell model, updating extraction tasks to capture LLM messages, and refining system prompts for structured extraction. Improved error handling and logging in extraction tasks, ensuring better traceability of LLM interactions. Updated GraphQL mutations to use transaction on commit for task execution. Added new migration for LLM call log field in Datacell model.
…al language. No longer needed.
…lyzers changing expected db conditions when looking for analyzers - can't assume analyzer table was empty anymore.
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.
Huge batch of changes marching towards v3.0.0 release. Functionality-wise, major addition is moving Notes, Annotations, Relationships, etc. to a "UnifiedContentFeed" where we can see all document content / filter / search / etch in one place. Have more plans to further streamline that approach. Fixed bugs with analyzers, exports, and extract functionality. Also fixed long-broken metadata feature and used same underlying datamodel as the extracts. Improved workflows on frontend to create new labels and labelsets.
UnifiedContentFeedFloatingDocumentControlsFloatingDocumentInputFloatingAnalysesPanelFloatingExtractsPanel