✅ 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:
71
node_modules/openai/pagination.js
generated
vendored
71
node_modules/openai/pagination.js
generated
vendored
@@ -1,6 +1,71 @@
|
||||
"use strict";
|
||||
// File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
|
||||
Object.defineProperty(exports, "__esModule", { value: true });
|
||||
const tslib_1 = require("./internal/tslib.js");
|
||||
/** @deprecated Import from ./core/pagination instead */
|
||||
tslib_1.__exportStar(require("./core/pagination.js"), exports);
|
||||
exports.CursorPage = exports.Page = void 0;
|
||||
const core_1 = require("./core.js");
|
||||
/**
|
||||
* Note: no pagination actually occurs yet, this is for forwards-compatibility.
|
||||
*/
|
||||
class Page extends core_1.AbstractPage {
|
||||
constructor(client, response, body, options) {
|
||||
super(client, response, body, options);
|
||||
this.data = body.data || [];
|
||||
this.object = body.object;
|
||||
}
|
||||
getPaginatedItems() {
|
||||
return this.data ?? [];
|
||||
}
|
||||
// @deprecated Please use `nextPageInfo()` instead
|
||||
/**
|
||||
* This page represents a response that isn't actually paginated at the API level
|
||||
* so there will never be any next page params.
|
||||
*/
|
||||
nextPageParams() {
|
||||
return null;
|
||||
}
|
||||
nextPageInfo() {
|
||||
return null;
|
||||
}
|
||||
}
|
||||
exports.Page = Page;
|
||||
class CursorPage extends core_1.AbstractPage {
|
||||
constructor(client, response, body, options) {
|
||||
super(client, response, body, options);
|
||||
this.data = body.data || [];
|
||||
this.has_more = body.has_more || false;
|
||||
}
|
||||
getPaginatedItems() {
|
||||
return this.data ?? [];
|
||||
}
|
||||
hasNextPage() {
|
||||
if (this.has_more === false) {
|
||||
return false;
|
||||
}
|
||||
return super.hasNextPage();
|
||||
}
|
||||
// @deprecated Please use `nextPageInfo()` instead
|
||||
nextPageParams() {
|
||||
const info = this.nextPageInfo();
|
||||
if (!info)
|
||||
return null;
|
||||
if ('params' in info)
|
||||
return info.params;
|
||||
const params = Object.fromEntries(info.url.searchParams);
|
||||
if (!Object.keys(params).length)
|
||||
return null;
|
||||
return params;
|
||||
}
|
||||
nextPageInfo() {
|
||||
const data = this.getPaginatedItems();
|
||||
if (!data.length) {
|
||||
return null;
|
||||
}
|
||||
const id = data[data.length - 1]?.id;
|
||||
if (!id) {
|
||||
return null;
|
||||
}
|
||||
return { params: { after: id } };
|
||||
}
|
||||
}
|
||||
exports.CursorPage = CursorPage;
|
||||
//# sourceMappingURL=pagination.js.map
|
||||
Reference in New Issue
Block a user