Replace invalid unicode with replacement chars

Description

Contributor guide

Tech stack

elixir

Domain

backend

Issue type

feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

needs investigation

Prerequisites

Elixir basicsJSON specification

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

40

Research direction

The issue proposes an optional mode to replace invalid unicode characters with replacement chars in the JSON parser. The implementation would require modifying the decoding logic, likely in `lib/jason.ex` or `lib/jason/decoder.ex`. The scope is unclear; the maintainer should clarify whether this should be a configurable option or always applied. Review the 4 comments on the issue for any additional context. It is advisable to first understand the current error handling for invalid unicode and then design a clean way to enable replacement.