Specification Compliance Misses

Open
#6,442 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

The payload names no source file, test or entry point, only an external compliance dashboard and a cJSON row that does not belong to this repository. Start by opening the linked report and identifying which specification test cases fail for jackson-databind, then reproduce one failing case locally. Done would mean a specific failing case is identified and either fixed or explained with a reference to the spec, which the issue itself does not define.

Written by the indexing model from the issue text.

Description

Hi,

We checked your library against the published specification, and it did not pass the compliance test.

You can view the details here: https://leo-gan.github.io/GLD.SerializerBenchmark/dashboard

To view your compliance report:

  1. Click 'Compliance'.
  2. Select your library's 'Language' and 'Standard'.
  3. Click on the cell corresponding to your library name and standard specification (e.g., Row: 'cJSON', Column: 'RFC 4627'). The cell will display your results (e.g., '87% / 296/342').

If you find any inaccuracies in the compliance report, please let us know.

Thank you for your work on the library. If you find our benchmark helpful, feel free to star our repository on GitHub: https://github.com/leo-gan/GLD.SerializerBenchmark

Best regards,

Dominant language
Java
Stars
3.8k
Forks
1.6k
Avg merge
1d 18h
Merged PRs (30d)
59

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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/jackson-databind

All issues in FasterXML/jackson-databind

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.