Tencent/APIJSON

[Feature] 对 PUT 默认支持条件，不传 @combine 也行

Open

#277 opened on Jul 30, 2021

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Java (2,229 forks)batch import
Enhancement 增强help wanted

Repository metrics

Stars
 (17,967 stars)
PR merge metrics
 (Avg merge 4h 34m) (1 merged PR in 30d)

Description

具体说下 目前不支持直接作为条件，如果不传 @combine 就报错了。 image

可以把带功能符号的键值对默认作为条件，例如 "content~": "a" "contactIdList<>": 82001 等。 判断方式为 StringUtil.isName(key) == false

为什么 方便使用，满足更多场景。

可能的问题： 前端过于灵活，后端可能不好保证安全？ 目前强制传 id / id{} ，应该能保证。不让前端传带功能符的键值对，应该后端 Request 表配置。

Contributor guide

Research direction
Study how APIJSON parses request parameters, especially the @combine directive and functional symbols like ~ and <>. Examine the PUT method's handling of conditions. Modify the logic to automatically treat keys with functional symbols as conditions when @combine is not provided. Consider security implications by ensuring that only allowed keys trigger conditions.
Tech stack
java
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Java
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65