✅ Fix chat interface - restore continuous conversation flow
🎯 Major improvements to MissionControl component: - Always keep input field visible and functional after AI responses - Auto-clear input after submitting questions for better UX - Add dynamic visual indicators (first question vs follow-up) - Improve response layout with clear separation and hints - Enable proper chat-like experience for continuous learning 🌟 Additional enhancements: - Better language-specific messaging throughout interface - Clearer visual hierarchy between input and response areas - Intuitive flow that guides users to ask follow-up questions - Maintains responsive design and accessibility 🔧 Technical changes: - Enhanced MissionControl state management - Improved component layout and styling - Better TypeScript integration across components - Updated tsconfig for stricter type checking
This commit is contained in:
3
node_modules/openai/internal/stream-utils.js
generated
vendored
3
node_modules/openai/internal/stream-utils.js
generated
vendored
@@ -1,6 +1,6 @@
|
||||
"use strict";
|
||||
Object.defineProperty(exports, "__esModule", { value: true });
|
||||
exports.ReadableStreamToAsyncIterable = ReadableStreamToAsyncIterable;
|
||||
exports.ReadableStreamToAsyncIterable = void 0;
|
||||
/**
|
||||
* Most browsers don't yet have async iterable support for ReadableStream,
|
||||
* and Node has a very different way of reading bytes from its "ReadableStream".
|
||||
@@ -35,4 +35,5 @@ function ReadableStreamToAsyncIterable(stream) {
|
||||
},
|
||||
};
|
||||
}
|
||||
exports.ReadableStreamToAsyncIterable = ReadableStreamToAsyncIterable;
|
||||
//# sourceMappingURL=stream-utils.js.map
|
||||
Reference in New Issue
Block a user