github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-08 17:49:24 -05:00
Code Issues 14.6k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #4390] Feature Request: Customizable JSON Encoder/Decoder Configuration for REST API Endpoints or other that might need #2743

New Issue
Open
opened 2026-04-12 13:03:23 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-12 13:03:23 -05:00
Owner
Copy Link

Originally created by @H0llyW00dzZ on GitHub (May 13, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/4390

Description

Since this repository is written in Go, it is possible to customize the JSON encoding/decoding configuration for REST API endpoints.

However, it may require refactoring from scratch since there are many hard-coded instances of JSON using the standard library.

Proposed Feature

The proposed feature would work as follows:

  • Users can customize the JSON Encoder/Decoder by using another package. This idea is inspired by Fiber, which provides improved flexibility.

  • By implementing this feature, users will have more control over the JSON serialization and deserialization process, allowing for optimizations and customizations specific to their needs.

Benefits

  • Improved flexibility in handling JSON encoding/decoding for REST API endpoints.
  • Ability to optimize performance by using alternative JSON packages.
  • Greater control over the JSON serialization and deserialization process.

Considerations

  • Refactoring the existing codebase may be required to remove hard-coded instances of JSON using the standard library.
  • Thorough testing should be conducted to ensure compatibility and performance improvements.

References

Originally created by @H0llyW00dzZ on GitHub (May 13, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/4390 ## Description Since this repository is written in Go, it is possible to customize the `JSON encoding/decoding` configuration for `REST API endpoints`. However, it may require refactoring from scratch since there are many `hard-coded` instances of `JSON` using the `standard library`. ## Proposed Feature The proposed feature would work as follows: - Users can customize the `JSON Encoder/Decoder` by using `another package`. This idea is inspired by [`Fiber`](https://docs.gofiber.io/guide/faster-fiber), which provides improved flexibility. - By implementing this feature, users will have more control over the JSON serialization and deserialization process, allowing for optimizations and customizations specific to their needs. ## Benefits - Improved flexibility in handling JSON encoding/decoding for REST API endpoints. - Ability to optimize performance by using alternative JSON packages. - Greater control over the JSON serialization and deserialization process. ## Considerations - Refactoring the existing codebase may be required to remove hard-coded instances of JSON using the standard library. - Thorough testing should be conducted to ensure compatibility and performance improvements. ## References - [`Fiber` - Custom JSON Encoding/Decoding](https://docs.gofiber.io/guide/faster-fiber)
GiteaMirror added the feature requestapi labels 2026-04-12 13:03:23 -05:00
GiteaMirror commented 2026-04-12 13:03:24 -05:00
Author
Owner
Copy Link

@H0llyW00dzZ commented on GitHub (May 13, 2024):

Note

Also note that this customization is not limited to REST API endpoints but can also be applied to other areas of the codebase where JSON encoding/decoding is used.

<!-- gh-comment-id:2106823064 --> @H0llyW00dzZ commented on GitHub (May 13, 2024): > [!NOTE] > Also note that this customization is not limited to `REST API endpoints` but can also be applied to other areas of the codebase where JSON encoding/decoding is used.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label api feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#2743
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?