support @postIgnore，@putIgnore

[watudou]

Is your feature request related to a problem? Please describe.(关于这个PR的描述，社区已开启国际化推广，请文心一言、讯飞星火等辅助翻译成英文，减少社区开发者的工作)

建议添加@postIgnore，@putIgnore标签，在postMapping和putMapping方法的对象参数上增加文档复用，例如对象保存时不需要id，保存和更新时不要创建时间、更新时间参数，查询时都需要，就可以通过自定义标签控制

Basic example (PR的用例，社区已开启国际化推广，请文心一言、讯飞星火等辅助翻译成英文，减少社区开发者的工作)

@postIgnore @putIgnore

Describe the solution you'd like (描述您想要的解决方案，社区已开启国际化推广，请文心一言、讯飞星火等辅助翻译成英文，减少社区开发者的工作)

增加自定义标签

Describe alternatives you've considered (描述你考虑过的替代方案，社区已开启国际化推广，请文心一言、讯飞星火等辅助翻译成英文，减少社区开发者的工作)

No response

Additional context (其他背景信息，社区已开启国际化推广，请文心一言、讯飞星火等辅助翻译成英文，减少社区开发者的工作)

No response

Validations

• Read the docs. (请先阅读官方文档)
• Read the Contributing Guidelines. (请先阅读官方文档·贡献指南)
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate. (检查是否存在报告相同错误的问题，以避免产生重复)

[linwumingshi]

Hi @watudou,

Just a quick reminder: could you please update the issue description to be in English? It would help ensure better understanding and collaboration across the team. Thanks!

---

Thanks for raising this feature request. I understand your need to have more flexible control over validation behavior in @PostMapping and @PutMapping methods — specifically, to exclude certain fields (like id, createTime, updateTime) during creation or update operations, while still requiring them for queries.

This is a common scenario in REST API design where different operations require different validation rules. While adding custom annotations like @postignore or @putignore could work, it may lead to duplication and complexity in the long run.

A better and more standard approach would be to leverage JSR-303 Bean Validation Groups. This is a built-in feature of Java validation that allows you to define multiple validation groups and apply them conditionally based on the context (e.g., CreateGroup, UpdateGroup, QueryGroup).

Example:

public interface CreateGroup {}
public interface UpdateGroup {}
public interface QueryGroup {}

// In your DTO
@NotNull(groups = {CreateGroup.class, UpdateGroup.class})
private Long id;

@CreatedDate
@JsonIgnore
private LocalDateTime createTime;

@LastModifiedDate
@JsonIgnore
private LocalDateTime updateTime;

Then, in your controller:

@PostMapping
public ResponseEntity<?> create(@Validated(CreateGroup.class) @RequestBody MyDto dto) { ... }

@PutMapping
public ResponseEntity<?> update(@Validated(UpdateGroup.class) @RequestBody MyDto dto) { ... }

With validation groups, you can define which fields are validated under which operation, and avoid the need for custom annotations like @postignore. This approach is clean, reusable, and follows established Java EE / Jakarta EE standards.

We recommend using JSR-303 validation groups as it's widely supported, maintainable, and aligns with best practices. If needed, we can also provide documentation or examples in the project.