0125c386ac
* fix(i18n): wrap hardcoded MCP auto-install strings with t() Adds mcp.serverNotRunning, mcp.installDisabledWarning, mcp.installTooltip, and mcp.failedToInstall keys to en.json and replaces the hardcoded strings in McpAuthSection, McpAutoInstallContent, and useMcpServer. Downloads updated translations for all 6 locale files from GP. * fix(i18n): wrap hardcoded playground no-input strings with t() Adds playground.runFlow and playground.noInputHint keys to en.json and replaces hardcoded strings in both no-input.tsx components (playgroundComponent and IOModal). Reuses flowBuild.stop for the Stop button. Uses Trans for the hint paragraph with embedded Chat Input link; works around react-i18next v16 conditional type by casting to React.FC<TransProps<string>>. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(i18n): route welcome-screen template apply through resetFlow for translations useApplyTemplateToCurrentFlow was calling setNodes() / setEdges() directly and then useFlowStore.setCurrentFlow() (metadata-only), bypassing the resetFlow → syncNodeTranslations pipeline. This meant component display names and descriptions were never translated to the active language when a user selected a starter template from the welcome overlay. Fix: use useFlowsManagerStore.setCurrentFlow() instead, which calls resetFlow and therefore syncNodeTranslations with the already-loaded typesStore data. Keep the direct setNodes/setEdges path as a fallback when currentFlow is null. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * chore(i18n): sync all locale files from GP Frontend: adds playground.runFlow and playground.noInputHint translations for all 6 locales (new keys from no-input component i18n work). Backend: adds template_notes.vector_store_rag.e8deaec6 (updated README note with docs.langflow.org URL replacing localhost), drops orphaned keys for renamed/removed components (chunkdoclingdocument, doclinginline) that no longer exist in en.json. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * [autofix.ci] apply automated fixes * fix: guard saveFlow rollback against stale flow reference Only restore the previous flow on save failure if the user hasn't already navigated to a different flow, preventing the rollback from clobbering a newer active selection. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(tests): fix CI failures in use-apply-template and no-input tests - Fix double-renamed declaration setCurrentFlowInManagerInManager → setCurrentFlowInManager - Fix mock state key from setCurrentFlowInManager to setCurrentFlow (matches hook's store selector) - Update test assertions to check setCurrentFlowInManager instead of setNodes/setEdges (hook routes through manager store when currentFlow exists) - Enhance jest.setup.js Trans mock to parse <N>text</N> i18nKey tags and render React elements from components prop (fixes "Add a" text not found in no-input test) * fix(frontend): fix Biome import order in playground no-input component --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Getting Started with Create React App
This project was bootstrapped with Create React App.
Available Scripts
In the project directory, you can run:
npm start
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
npm test
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
npm run build
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
npm run eject
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
Learn More
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.