jc
> The current situation is that an incorrect JSON format returns `unexpected EOF`. After this PR, it will return the error `invalid json` Hello, my previous description might not have...
@appleboy PTAL
Please take a look at this if you have time @shenqidebaozi. For users, there will be deviations in the use of EncodeURL. There are already multiple issues that have feedback...
> Is it necessary to process in encoding and can it be processed in gen code是否需要在编码中处理，是否可以在 gen code 中处理 What does `gen code` mean? Since the code specifies using json...
I think `enterprise_id` and `enterpriseId` should be two different params in the URL? If your param is `enterprise_id` should add `[json_name = "enterprise_id"]` in the field.
Hi, can I add this method? If so, is it reasonable to add it this way, or should it be placed in the driver? @jinzhu
> Maybe we should place it in a helper package, keeping GORM itself clean and avoiding adding too much API directly. Do you mean the helper package under the go-gorm...
> For now, we probably won’t maintain an additional helper package. It could be placed in a separate third-party library for the time being. ok