Tencent/APIJSON

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

Open

#277 opened on Jul 30, 2021

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

Description

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

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

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

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

Contributor guide

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-2 days
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.
mostly clear
Prerequisites
Java programmingAPIJSON basicsunderstanding of condition parsing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Examine the PUT request handling in the APIJSON source, likely in the RequestParser or similar class, to understand how conditions are currently processed and where @combine is required. Implement logic to treat keys with functional symbols (e.g., ending with '~' or '<>') as implicit conditions without needing an explicit @combine, using StringUtil.isName() as suggested. Ensure security by restricting such functional keys to backend configuration rather than allowing frontend control.