-
Notifications
You must be signed in to change notification settings - Fork 0
Dev #20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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
- Added `export const dynamic = "force-dynamic";` to various API route files to ensure they are rendered dynamically. - Updated routes in `admin/memory`, `proxy`, `saved-searches`, and others to improve responsiveness and data fetching. This change enhances the application's performance by ensuring that all relevant routes are dynamically rendered, allowing for better handling of data and user interactions.
- Updated the `getFeedHealth`, `getBulkFeedHealth`, and `getUnhealthyFeeds` functions to use nullish coalescing for `consecutiveFailures`, ensuring it defaults to 0 if undefined. - Modified the `recordFeedFailure` function to handle undefined `autoDisableThreshold`, defaulting to 10 if not set. These changes enhance the robustness of feed health metrics by preventing errors related to undefined values, improving overall data integrity.
- Removed the redundant `pendingDeleteEmbeddings` check from the button's `disabled` property in the LLMConfigTab component. - This change simplifies the button's state management, ensuring it only reflects the `deleteEmbeddings.isPending` status. These modifications enhance code clarity and maintainability in the LLM configuration interface.
…ut files - Added `export const runtime = "nodejs";` to both `layout.tsx` and `docs/layout.tsx` to ensure compatibility with Node.js. - Set `export const revalidate = 0;` in both files to disable static optimization, allowing for immediate updates on content changes. These changes enhance the application's rendering behavior by ensuring it operates in a Node.js environment and updates content dynamically without caching delays.
- Added ".source" to the exclude list in tsconfig.json to prevent TypeScript from processing generated files. This change improves the project's build process by ensuring that unnecessary files are not included, enhancing overall maintainability.
- Added functionality to update the embedding provider in the LLMConfigTab component when the provider changes. - Updated API routes to include new fields for model and provider sources in the embedding configuration. - Refactored the getEmbeddingConfiguration function to retrieve model settings alongside existing configurations. These changes improve the LLM configuration interface by allowing dynamic updates to the embedding provider, enhancing user experience and configuration flexibility.
- Changed the default value of `autoMarkAsRead` from false to true in multiple components and configuration files. - Updated the documentation to reflect this change in user preferences. These modifications enhance user experience by ensuring articles are automatically marked as read when opened, aligning with expected behavior.
- Removed the try-catch block in the related articles API route to streamline the flow of fetching related articles. - Updated the `findRelatedArticles` function to return an empty array when an article has no embedding, improving clarity and reducing unnecessary error handling. These changes enhance the readability and maintainability of the code by simplifying the error handling logic while ensuring consistent behavior when no related articles are found.
…vice - Replaced direct JSON parsing with a dedicated `parseJSONFromLLM` function in both the Ollama and OpenAI LLM providers, enhancing error handling and maintainability. - Updated the summarization service to utilize the new parsing function, ensuring consistent behavior across LLM interactions. - Improved logging messages to provide clearer context during fallback scenarios. These changes streamline the JSON parsing process, reduce code duplication, and enhance the overall robustness of LLM-related functionalities.
- Added exclusions for generated and third-party files in the ESLint configuration to enhance linting accuracy. - Refactored the `ReadingPanelLayout` component to utilize `useMemo` for computing children content, reducing unnecessary re-renders and improving performance. - Updated various components to use `Link` from Next.js instead of anchor tags for better routing practices. - Enhanced user feedback in the `CategoryView` and `FeedDetailsView` components by replacing HTML entities with their corresponding characters for improved readability. These changes contribute to better code quality, performance optimizations, and adherence to best practices in component rendering and routing.
- Removed the ".source" directory from the exclude list in tsconfig.json to ensure TypeScript processes relevant files correctly. - Added React import to the Tabs story file for proper component rendering and removed unnecessary comments. These changes enhance the TypeScript configuration and ensure the Tabs component story functions correctly with React.
- Added ".source" to the exclude list in tsconfig.json to prevent TypeScript from processing unnecessary files, improving the project's build process and maintainability. This change ensures that only relevant files are included in the TypeScript compilation, aligning with best practices for project configuration.
- Changed the import path for the `docs` module from a relative path to a named import from `fumadocs-mdx:collections/server`. This adjustment improves clarity and aligns with the project's module structure. This change ensures that the documentation source is correctly referenced, enhancing maintainability and consistency in the codebase.
- Added error handling in the feed validation process to return a meaningful message when feed information cannot be fetched. - Updated the feed creation process to accept an optional settings parameter for extraction methods, allowing for more flexible feed management. - Enhanced the OverviewView component with a button to add new feeds, improving user interaction and accessibility. - Implemented changes to ensure that feeds are parsed correctly, handling cases where feeds return a 304 Not Modified response. These updates improve the overall user experience and robustness of the feed management system, ensuring better error handling and user engagement.
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.
No description provided.