github-starred/yaak
2
0
Fork 0
mirror of https://github.com/mountain-loop/yaak.git synced 2026-05-07 02:21:59 -05:00
Code Issues 71 Packages Projects Releases 101 Wiki Activity

[PR #358] feat: implement layered settings system for HTTP requests and folders #636

New Issue
Open
opened 2026-04-16 15:20:34 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-16 15:20:34 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/mountain-loop/yaak/pull/358
Author: @gschier
Created: 1/10/2026
Status: 🔄 Open

Base: main ← Head: omnara/premium-deviator

📝 Commits (2)

  • 4b7497a feat: implement layered settings system for HTTP requests and folders
  • 0a52032 Merge branch 'main' into omnara/premium-deviator

📊 Changes

7 files changed (+161 additions, -20 deletions)

View changed files

📝 crates-tauri/yaak-app/src/http_request.rs (+7 -4)
📝 crates-tauri/yaak-app/src/lib.rs (+2 -2)
📝 crates-tauri/yaak-app/src/ws_ext.rs (+1 -1)
➕ crates/yaak-models/migrations/20260109201041_layered_settings.sql (+9 -0)
📝 crates/yaak-models/src/models.rs (+64 -10)
📝 crates/yaak-models/src/queries/http_requests.rs (+76 -1)
📝 crates/yaak-models/src/queries/workspaces.rs (+2 -2)

📄 Description

Add support for settings overrides at folder and HTTP request levels. Introduces nullable settings columns to database tables and implements resolution logic to merge workspace, folder, and request-level settings with proper precedence.

🔄 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/mountain-loop/yaak/pull/358 **Author:** [@gschier](https://github.com/gschier) **Created:** 1/10/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `omnara/premium-deviator` --- ### 📝 Commits (2) - [`4b7497a`](https://github.com/mountain-loop/yaak/commit/4b7497a908dfc5aff31ee62c6ba15e535e2d6237) feat: implement layered settings system for HTTP requests and folders - [`0a52032`](https://github.com/mountain-loop/yaak/commit/0a520329887a5fd6ff00c1676423971e6b088f81) Merge branch 'main' into omnara/premium-deviator ### 📊 Changes **7 files changed** (+161 additions, -20 deletions) <details> <summary>View changed files</summary> 📝 `crates-tauri/yaak-app/src/http_request.rs` (+7 -4) 📝 `crates-tauri/yaak-app/src/lib.rs` (+2 -2) 📝 `crates-tauri/yaak-app/src/ws_ext.rs` (+1 -1) ➕ `crates/yaak-models/migrations/20260109201041_layered_settings.sql` (+9 -0) 📝 `crates/yaak-models/src/models.rs` (+64 -10) 📝 `crates/yaak-models/src/queries/http_requests.rs` (+76 -1) 📝 `crates/yaak-models/src/queries/workspaces.rs` (+2 -2) </details> ### 📄 Description Add support for settings overrides at folder and HTTP request levels. Introduces nullable settings columns to database tables and implements resolution logic to merge workspace, folder, and request-level settings with proper precedence. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-16 15:20:34 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
pull-request
Mirrored from GitHub Pull Request
No Label pull-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/yaak#636
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?