Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

escapeString compatibility with encoding/json #87

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Commits on Jan 16, 2023

  1. Updated escapeString to be compatible with RFC4627

    and `encoding/json` from standard library
    barkyq committed Jan 16, 2023
    Configuration menu
    Copy the full SHA
    656593a View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    a5e2f25 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    788345a View commit details
    Browse the repository at this point in the history

Commits on Jan 18, 2023

  1. Configuration menu
    Copy the full SHA
    041656e View commit details
    Browse the repository at this point in the history
  2. forward solidus is not supposed to be escaped

    it is in range 0x23-0x5B see page 8 of:
    https://www.rfc-editor.org/rfc/rfc8259.html
    
    this should not be a problem though, if the unescape is applied to
    properly escaped json data
    barkyq committed Jan 18, 2023
    Configuration menu
    Copy the full SHA
    7a86309 View commit details
    Browse the repository at this point in the history
  3. Revert "forward solidus is not supposed to be escaped"

    This reverts commit 7a86309.
    barkyq committed Jan 18, 2023
    Configuration menu
    Copy the full SHA
    bb10766 View commit details
    Browse the repository at this point in the history