Added loginPage #1049
Added loginPage #1049
Conversation
- Create SettingsDisplay component - Display graphQueryMaxDepth and graphMinDegree - Position display at bottom-left corner
- Remove redundant label caching logic - Add graphLabels state to graph store
- Raised max layout iterations to 30 - Set default iterations to 15
- Move i18n initialization to async function - Sync i18n with settings store language - Add Root component for i18n loading state - Convert i18n.js to TypeScript
- Optimize graph data fetching conditions - Add isFetching state to prevent duplicate requests - Improve label selection handling
- Add NoCacheStaticFiles class - Set Cache-Control headers for HTML files
- Add `t` to `GraphLabels` dependency array - Add `isFetching` to `useLightragGraph` dependencies
- Updated settings version and added new graph features - Added enableNodeDrag setting - Added enableHideUnselectedEdges - Disabled edge events by default - Set graphMinDegree to 0
- Set OpenAPI schema URL to `/openapi.json` - Set docs URL to `/docs` - Set redoc URL to `/redoc` - Update Vite config for API docs routing - Ensure proper path handling for docs endpoints
- Introduced TabVisibilityProvider component - Created TabContent for conditional rendering - Added context and hooks for tab visibility - Updated DocumentManager dependencies - Integrated provider in App component
…ility • Reset graph data without recreating instance • Fix search result caching on graph updates
…h viewer • Force mount inactive tabs • Maintain WebGL context across tab switches • Add visibility styles to TabsContent • Update conditional rendering logic
|
Welcome to the LightRAG community, and thanks for your contribution. The landing page is indeed a much-needed functionality. Since we have made several optimizations and evolutions to our WebUI, with some restructuring of the underlying architecture, certain features (such as language selection) overlap with what you have developed. Therefore, before we proceed with further review of your code, we need you to merge the improve-property-tooltip branch from the repository, resolve any conflicts, make appropriate integrations, and then submit again. Once again, thank you for your contribution to the community. |
|
You can refer to #1064 for what improve-property-tooltip is about. Any recommendation is welcome. |
Add the webuiInitialize variable, dev: '', build:'/webui'
|
As you said, all the work has been completed. I see that you have added a settings dropdown menu, which is indeed a better interaction when it comes to themes in more than 2 languages. Additionally, I have added an exit button |
Description
Added a login page, optional through .evn variable settings
Related Issues
[Reference any related issues or tasks addressed by this pull request.]
#1000
#1039
Checklist
Additional Notes
[Add any additional notes or context for the reviewer(s).]