mirror of
https://github.com/langgenius/dify.git
synced 2026-09-05 00:31:19 +08:00
be6612f454
Reintroduce the nullable api_tokens.dataset_id column (dropped in 2e9819ca5b28) so dataset API keys can opt into per-knowledge-base scoping: - NULL dataset_id keeps today's workspace-wide behavior, so every existing key and the existing /datasets/api-keys create route are unchanged. - validate_dataset_token rejects a bound key for any other dataset, and for endpoints that carry no dataset id (e.g. list-all), with 403. - CachedApiToken carries dataset_id with a None default so cache entries written before deploy keep deserializing. - The per-dataset console routes in apikey.py (previously dead code that 500ed on a missing ApiToken.dataset_id) now create bound keys; their list returns bound keys plus workspace keys so the dataset page shows the full access picture. - Frontend: the knowledge base API access popover gains an API keys entry; the secret key modal accepts datasetId, shows a scope column, and offers a workspace / this-knowledge-base scope choice on create. New strings are localized for all 23 locales.
77 lines
5.9 KiB
JSON
77 lines
5.9 KiB
JSON
{
|
|
"actionMsg.deleteConfirmTips": "This action cannot be undone.",
|
|
"actionMsg.deleteConfirmTitle": "Delete this secret key?",
|
|
"actionMsg.ok": "OK",
|
|
"apiKey": "API Key",
|
|
"apiKeyModal.apiSecretKey": "API Secret key",
|
|
"apiKeyModal.apiSecretKeyTips": "To prevent API abuse, protect your API Key. Avoid using it as plain text in front-end code. :)",
|
|
"apiKeyModal.createNewSecretKey": "Create new Secret key",
|
|
"apiKeyModal.created": "CREATED",
|
|
"apiKeyModal.generateTips": "Keep this key in a secure and accessible place.",
|
|
"apiKeyModal.lastUsed": "LAST USED",
|
|
"apiKeyModal.scope": "SCOPE",
|
|
"apiKeyModal.scopeAllDatasets": "All knowledge bases",
|
|
"apiKeyModal.scopeBoundDataset": "Single knowledge base",
|
|
"apiKeyModal.scopeThisDataset": "This knowledge base only",
|
|
"apiKeyModal.secretKey": "Secret Key",
|
|
"apiServer": "API Server",
|
|
"chatMode.blocking": "Blocking type, waiting for execution to complete and returning results. (Requests may be interrupted if the process is long)",
|
|
"chatMode.chatMsgHistoryApi": "Get the chat history message",
|
|
"chatMode.chatMsgHistoryApiTip": "The first page returns the latest `limit` bar, which is in reverse order.",
|
|
"chatMode.chatMsgHistoryConversationIdTip": "Conversation ID",
|
|
"chatMode.chatMsgHistoryFirstId": "ID of the first chat record on the current page. The default is none.",
|
|
"chatMode.chatMsgHistoryLimit": "How many chats are returned in one request",
|
|
"chatMode.conversationIdTip": "(Optional) Conversation ID: leave empty for first-time conversation; pass conversation_id from context to continue dialogue.",
|
|
"chatMode.conversationRenamingApi": "Conversation renaming",
|
|
"chatMode.conversationRenamingApiTip": "Rename conversations; the name is displayed in multi-session client interfaces.",
|
|
"chatMode.conversationRenamingNameTip": "New name",
|
|
"chatMode.conversationsListApi": "Get conversation list",
|
|
"chatMode.conversationsListApiTip": "Gets the session list of the current user. By default, the last 20 sessions are returned.",
|
|
"chatMode.conversationsListFirstIdTip": "The ID of the last record on the current page, default none.",
|
|
"chatMode.conversationsListLimitTip": "How many chats are returned in one request",
|
|
"chatMode.createChatApi": "Create chat message",
|
|
"chatMode.createChatApiTip": "Create a new conversation message or continue an existing dialogue.",
|
|
"chatMode.info": "For versatile conversational apps using a Q&A format, call the chat-messages API to initiate dialogue. Maintain ongoing conversations by passing the returned conversation_id. Response parameters and templates depend on Dify Prompt Eng. settings.",
|
|
"chatMode.inputsTips": "(Optional) Provide user input fields as key-value pairs, corresponding to variables in Prompt Eng. Key is the variable name, Value is the parameter value. If the field type is Select, the submitted Value must be one of the preset choices.",
|
|
"chatMode.messageFeedbackApi": "Message terminal user feedback, like",
|
|
"chatMode.messageFeedbackApiTip": "Rate received messages on behalf of end-users with likes or dislikes. This data is visible in the Logs & Annotations page and used for future model fine-tuning.",
|
|
"chatMode.messageIDTip": "Message ID",
|
|
"chatMode.parametersApi": "Obtain application parameter information",
|
|
"chatMode.parametersApiTip": "Retrieve configured Input parameters, including variable names, field names, types, and default values. Typically used for displaying these fields in a form or filling in default values after the client loads.",
|
|
"chatMode.queryTips": "User input/question content",
|
|
"chatMode.ratingTip": "like or dislike, null is undo",
|
|
"chatMode.streaming": "streaming returns. Implementation of streaming return based on SSE (Server-Sent Events).",
|
|
"chatMode.title": "Chat App API",
|
|
"completionMode.blocking": "Blocking type, waiting for execution to complete and returning results. (Requests may be interrupted if the process is long)",
|
|
"completionMode.createCompletionApi": "Create Completion Message",
|
|
"completionMode.createCompletionApiTip": "Create a Completion Message to support the question-and-answer mode.",
|
|
"completionMode.info": "For high-quality text generation, such as articles, summaries, and translations, use the completion-messages API with user input. Text generation relies on the model parameters and prompt templates set in Dify Prompt Engineering.",
|
|
"completionMode.inputsTips": "(Optional) Provide user input fields as key-value pairs, corresponding to variables in Prompt Eng. Key is the variable name, Value is the parameter value. If the field type is Select, the submitted Value must be one of the preset choices.",
|
|
"completionMode.messageFeedbackApi": "Message feedback (like)",
|
|
"completionMode.messageFeedbackApiTip": "Rate received messages on behalf of end-users with likes or dislikes. This data is visible in the Logs & Annotations page and used for future model fine-tuning.",
|
|
"completionMode.messageIDTip": "Message ID",
|
|
"completionMode.parametersApi": "Obtain application parameter information",
|
|
"completionMode.parametersApiTip": "Retrieve configured Input parameters, including variable names, field names, types, and default values. Typically used for displaying these fields in a form or filling in default values after the client loads.",
|
|
"completionMode.queryTips": "User input text content.",
|
|
"completionMode.ratingTip": "like or dislike, null is undo",
|
|
"completionMode.streaming": "streaming returns. Implementation of streaming return based on SSE (Server-Sent Events).",
|
|
"completionMode.title": "Completion App API",
|
|
"copied": "Copied",
|
|
"copy": "Copy",
|
|
"develop.noContent": "No content",
|
|
"develop.pathParams": "Path Params",
|
|
"develop.query": "Query",
|
|
"develop.requestBody": "Request Body",
|
|
"develop.toc": "Contents",
|
|
"disabled": "Disabled",
|
|
"loading": "Loading",
|
|
"merMaid.rerender": "Redo Rerender",
|
|
"never": "Never",
|
|
"ok": "In Service",
|
|
"pause": "Pause",
|
|
"play": "Play",
|
|
"playing": "Playing",
|
|
"regenerate": "Regenerate",
|
|
"status": "Status"
|
|
}
|