langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-22 01:55:27 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

[PR #617] [MERGED] feat: add structrued output to ollama #1465

New Issue
Closed
opened 2026-02-16 10:23:01 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 10:23:01 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-official-plugins/pull/617
Author: @Nov1c444
Created: 3/31/2025
Status: ✅ Merged
Merged: 4/7/2025
Merged by: @crazywoola

Base: main ← Head: feat/ollama-add-format

📝 Commits (2)

  • 271384f feat: add structrued output to ollama
  • 88c09e5 chore: bump version

📊 Changes

2 files changed (+24 additions, -8 deletions)

View changed files

📝 models/ollama/manifest.yaml (+7 -7)
📝 models/ollama/models/llm/llm.py (+17 -1)

📄 Description

Related Issue or Context

Add response_format field to ollama to support structured output

Type of Change

  • Bug Fix (non-breaking change which fixes an Issue)
  • New Feature (non-breaking change which adds Functionality)
  • Breaking Change (fix or feature that may cause existing Functionality to not work as expected)
  • Documentation Update
  • Code Refactoring
  • Other

Version Control (if applicable)

  • Version bumped in Manifest.yaml (top-level Version field, not in Meta section)

Test Evidence (if applicable)

Important

Visual Proof is required for Bug Fixes, New Features, and Breaking Changes:

Screenshots or Video/GIF:

image

Note

For Non-LLM Models Changes:

  • Bug Fixes:
    • Show the Fix working
  • New Features:
    • Demonstrate the Functionality
  • Breaking Changes:
    • Show both Old and New Behavior

For LLM Models Changes:
LLM Models Test Example

  • Bug Fixes:
    • Show the Fix working with Example Inputs/Outputs
  • New Features:
    • Demonstrate the Functionality with Example Inputs/Outputs
  • Breaking Changes (requires comprehensive Testing):
    • Conversation & Interaction:
      • Message Flow Handling (System Messages and User→Assistant Turn-taking)
      • Tool Interaction Flow (Multi-round Usage and Output Handling if applicable)
    • Input/Output Handling:
      • Multimodal Input Handling (Images, PDFs, Audio, Video if applicable)
      • Multimodal Output Generation (Images, Audio, Video if applicable)
      • Structured Output Format (if applicable)
    • Metrics:
      • Token Consumption Metrics
    • Others:
      • e.g., Reasoning Process for Claude 3.7 Sonnet, Grounding for Gemini (if applicable)

Environment Verification

Important

At least one environment must be tested.

Local Deployment Environment

Local Deployment Dify Version:
  • Changes tested in an Isolated Environment that matches Production Configuration
  • No Cached Data influenced the Test Results

SaaS Environment

  • Testing performed on cloud.dify.ai

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-official-plugins/pull/617 **Author:** [@Nov1c444](https://github.com/Nov1c444) **Created:** 3/31/2025 **Status:** ✅ Merged **Merged:** 4/7/2025 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `feat/ollama-add-format` --- ### 📝 Commits (2) - [`271384f`](https://github.com/langgenius/dify-official-plugins/commit/271384f3933ba1baff2f59634a24ca096b04a2a5) feat: add structrued output to ollama - [`88c09e5`](https://github.com/langgenius/dify-official-plugins/commit/88c09e5b7aeb62d8718aaa9a50af77189f4da2f5) chore: bump version ### 📊 Changes **2 files changed** (+24 additions, -8 deletions) <details> <summary>View changed files</summary> 📝 `models/ollama/manifest.yaml` (+7 -7) 📝 `models/ollama/models/llm/llm.py` (+17 -1) </details> ### 📄 Description ## Related Issue or Context Add response_format field to ollama to support structured output ## Type of Change <!-- Put an `x` in all the boxes that apply --> - [ ] Bug Fix (non-breaking change which fixes an Issue) - [x] New Feature (non-breaking change which adds Functionality) - [ ] Breaking Change (fix or feature that may cause existing Functionality to not work as expected) - [ ] Documentation Update - [ ] Code Refactoring - [ ] Other ## Version Control (if applicable) - [ ] Version bumped in Manifest.yaml (top-level `Version` field, not in Meta section) <!-- Version format: MAJOR.MINOR.PATCH - MAJOR (0.x.x): Reserved for Major Releases with widespread Breaking Changes - MINOR (x.0.x): For New Features or limited Breaking Changes - PATCH (x.x.0): For backwards-compatible Bug Fixes and minor Improvements - Note: Each version component (MAJOR, MINOR, PATCH) can be 2 digits, e.g., 10.11.22 --> ## Test Evidence (if applicable) > [!IMPORTANT] > Visual Proof is required for Bug Fixes, New Features, and Breaking Changes: ### Screenshots or Video/GIF: <img width="1512" alt="image" src="https://github.com/user-attachments/assets/324082f8-3ef3-485c-85c2-b05c3dbe6d53" /> > [!NOTE] > For Non-LLM Models Changes: > - **Bug Fixes**: > - [ ] Show the Fix working > - **New Features**: > - [ ] Demonstrate the Functionality > - **Breaking Changes**: > - [ ] Show both Old and New Behavior > > For LLM Models Changes: > [LLM Models Test Example](https://github.com/langgenius/dify-official-plugins/blob/main/.assets/test-examples/llm-plugin-tests/llm_test_example.md) > - **Bug Fixes**: > - [ ] Show the Fix working with Example Inputs/Outputs > - **New Features**: > - [x] Demonstrate the Functionality with Example Inputs/Outputs > - **Breaking Changes** (requires comprehensive Testing): > - **Conversation & Interaction**: > - [ ] Message Flow Handling (System Messages and User→Assistant Turn-taking) > - [ ] Tool Interaction Flow (Multi-round Usage and Output Handling if applicable) > - **Input/Output Handling**: > - [ ] Multimodal Input Handling (Images, PDFs, Audio, Video if applicable) > - [ ] Multimodal Output Generation (Images, Audio, Video if applicable) > - [ ] Structured Output Format (if applicable) > - **Metrics**: > - [ ] Token Consumption Metrics > - **Others**: > - [ ] e.g., Reasoning Process for Claude 3.7 Sonnet, Grounding for Gemini (if applicable) ### Environment Verification > [!IMPORTANT] > At least one environment must be tested. #### Local Deployment Environment ##### Local Deployment Dify Version: <!-- Specify your version (e.g., 1.1.3) --> - [ ] Changes tested in an Isolated Environment that matches Production Configuration <!-- - Python virtual env matching Manifest.yaml & requirements.txt - No breaking changes in Dify that may affect the testing result --> - [ ] No Cached Data influenced the Test Results #### SaaS Environment - [ ] Testing performed on cloud.dify.ai --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-16 10:23:01 -05:00
yindo closed this issue 2026-02-16 10:23:01 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#1465
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?