9dc6c24180* ✨ (inputs.py): Update default prompt input types to include "MessageTextInput" for improved user experience 📝 (styleUtils.ts): Add color definition for "MessageTextInput" node to enhance visual representation in the frontend * 📝 (text.py): Update input_types for "Value" to include "Message" for better clarity 📝 (memory.py): Update input_types for "Session ID" to include "Message" for consistency 📝 (message.py): Update input_types for "Session ID" to include "Message" for uniformity 📝 (self_query.py): Update input_types for "Query" to only include "Message" for consistency 📝 (create_data.py): Update input_types for fields to only include "Message" for consistency 📝 (update_data.py): Update input_types for fields to only include "Message" for consistency 📝 (inputs.py): Update DEFAULT_PROMPT_INTUT_TYPES to only include "Message" for consistency 📝 (styleUtils.ts): Remove "MessageTextInput" from nodeColors and nodeColorsName for consistency * 📝 (model.py): update display name from "Text" to "Message" for better clarity 📝 (url.py): update display name from "Text" to "Message" for better consistency 📝 (memory.py): update display name from "Text" to "Message" for better understanding 📝 (text.py): update display name from "Text" to "Message" for better semantics 📝 (llm_math.py): update display name from "Text" to "Message" for improved readability 📝 (runnable_executor.py): update display name from "Text" to "Message" for better context 📝 (sql_generator.py): update display name from "Text" to "Message" for clearer communication 📝 (text.py): update display name from "Text" to "Message" for better consistency 📝 (parse_data.py): update display name from "Text" to "Message" for enhanced understanding 📝 (wikidata_api.py): update display name from "Text" to "Message" for improved semantics 📝 (test_cycles.py): update display name from "Text" to "Message" for better clarity * [autofix.ci] apply automated fixes * 🔧 (App.css): change width property value to fit-content to improve layout responsiveness * fix: resolve merge conflicts and clean up URLComponent implementation in starter projects - Removed conflicting sections in the JSON files for 'Custom Component Maker' and 'Graph Vector Store RAG'. - Ensured the URLComponent class is correctly defined with methods for URL validation and content fetching. - Updated input and output definitions for better clarity and functionality. * 🐛 (freeze.spec.ts): fix incorrect test selectors for handle-textinput-shownode and handle-parsedata-shownode elements to match updated element IDs * 📝 (NodeOutputfield/index.tsx): Add id prop to InspectButton component for better identification 🔧 (freeze-path.spec.ts, freeze.spec.ts, stop-building.spec.ts, decisionFlow.spec.ts, similarity.spec.ts, textInputOutput.spec.ts, generalBugs-shard-5.spec.ts, fileUploadComponent.spec.ts): Update test selectors to match changes in UI components for better test accuracy * ✨ (duckduckgo.spec.ts): update the test to click on a specific element with the test ID "output-inspection-data-duckduckgosearch" instead of "output-inspection-data" to match the updated frontend implementation. * ✨ (youtube-transcripts.spec.ts): update selector for clicking on transcript element to match changes in the frontend code, ensuring the test remains accurate --------- Co-authored-by: Gabriel Luiz Freitas Almeida <gabriel@langflow.org> Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| .dspy_cache | ||
| public | ||
| src | ||
| tests | ||
| .dockerignore | ||
| .eslintrc.json | ||
| .gitignore | ||
| .prettierignore | ||
| .prettierrc.mjs | ||
| cdk.Dockerfile | ||
| dev.Dockerfile | ||
| Dockerfile | ||
| favicon-new.ico | ||
| index.html | ||
| nginx.conf | ||
| package-lock.json | ||
| package.json | ||
| playwright.config.ts | ||
| postcss.config.js | ||
| README.md | ||
| run-tests.sh | ||
| set_proxy.sh | ||
| start-nginx.sh | ||
| tailwind.config.mjs | ||
| tsconfig.json | ||
| vite.config.mts | ||
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.