Skitii

Results 7 comments of Skitii

> 是的,更新还好搞一些,PUT 操作可以把 item key 放在 body 里面,查询和删除这两个操作比较麻烦,GET 和 DELETE 只能放在 url path 上 what if we just encode/decode the item key ? we can provide new interface on get/update/delete...

take getItem as an example, when we called getItem with openapi client, we can encode the key like the follow way, ``` String encode = new String(Base64.getEncoder().encode(key.getBytes(StandardCharsets.UTF_8))); OpenApiPathBuilder pathBuilder =...

Test example: ![企业微信截图_1c35ab62-226e-4344-8a13-ff877a257e5e](https://user-images.githubusercontent.com/50099513/186046172-df302291-025f-4111-ab4b-024c601ec20d.png) Test Result: ![企业微信截图_37a85783-b41c-4fbd-a744-26ea074f5959](https://user-images.githubusercontent.com/50099513/186046207-6957b783-e406-48ee-8ae4-cbba2c05f382.png)

wow, this way is more practicable, in the normal sutuation, it works like the old workflow, and we just use little cost to deal with unexpectable key, I'll try this....

@strongduanmu this issue has fixed in this pr(#27228), can be marked as completed.

@strongduanmu please assign to me.