Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

support jsonpointer format as rfc6901

Open
#71 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
backend

Research direction

Start by inspecting the existing json_pointer handling around PointerType and AtPointer, using the issue's Object/0/New_object example as the input case. Done means determining whether an RFC6901-style string can be accepted and transferred into the pointer components needed by AtPointer.

Written by the indexing model from the issue text.

Description

good first issue help wanted

Hi,
Does sonic-cpp support merge-patch easily?
For example : { op: replace, patch : "Object/0/New_object", value : "123" }

If use json_pointer:
sonic_json::Node* node2 = doc.AtPointer(PointerType({"Object", 0, "New_object"}));
This doesn't format well. transfer patch : "Object/0/New_object" to {"Object", 0, "New_object"}

Dominant language
C++
Stars
976
Forks
128
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 bytedance/sonic-cpp

All issues in bytedance/sonic-cpp

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.