Allow combination of `@JsonValue`, `@JsonRawValue` somehow

Open
#29 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale

Research direction

No files, tests, or entry points are named. Start by reading the linked jackson-databind issue and comparing the current meanings of @JsonValue and @JsonRawValue; define a compatible API for combining them and tests that establish the intended serialized output.

Written by the indexing model from the issue text.

Description

enhancement

(for background see https://github.com/FasterXML/jackson-databind/issues/1938)

Although naming of @JsonRawValue might indicate combination of @JsonValue and "do not encode", it actually works as refinement for regular properties, that is, combination of @JsonProperty and "do not encode".

But in some cases it would be beneficial to allow former interpretation.

One possibility would be to add a new property in @JsonValue -- this seem more natural than doing the reverse (adding something in @JsonRawValue to indicate "this is the sole output like @JsonValue, not property).

Dominant language
No language data
Stars
6
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from FasterXML/jackson3-dev

All issues in FasterXML/jackson3-dev

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.