micronaut-projects / micronaut-projects/micronaut-serialization

`SnakeCaseStrategy` produces duplicated json

Open
#147 2 comments 0 reactions 0 assignees View on GitHub
status: awaiting feedback
Dominant language
Java
Stars
36
Forks
29
Avg merge
1d 21h
Merged PRs (30d)
29

Description

### Expected Behavior

Serialization as usual
as with
image

### Actual Behaviour

image
or with native annotation
image
other strategy works fine for some reason
image

### Steps To Reproduce

I tried to reproduce with Spok in `JsonNamingSpec.groovy` but couldn't.
I guess it's again some strange combo of dependencies, or something else.
No custom mapper, Serde, no configuration in application.yml nothing special about the setup. Maybe it's a regression in RC-x versions. Not sure.
Pojo is primitive.
```java
@Value
@Builder(toBuilder = true)
class Pojo {
UUID uuid;
Instant timestamp;
}
```

### Environment Information

Serde RC-2
Java 11

### Example Application

_No response_

### Version

3.3.3

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the existing JsonNamingSpec.groovy reproduction attempt and compare SnakeCaseStrategy with the native annotation and another naming strategy under Java 11 and Serde RC-2. A useful outcome is a focused reproduction or regression test showing whether serialization emits duplicated JSON; the issue currently provides no example application or confirmed failing setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend-api-design
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.