Skip to content

JSONObject include #51

@mpetrik-phrase

Description

@mpetrik-phrase

Description of the Bug

Version 3.35.0 removed usage of custom JSONObject from com.chargebee.org.json.JSONObject. In the latest version 3.36.0 it looks to be back.

My question is: was it a mistake in 3.35.0 or is it a mistake now or is it intentional?

Thank you

Steps to reproduce

  1. Update to version 3.35.0 - change all your implementations to use org.json.JSONObject instead of com.chargebee.org.json.JSONObject.
  2. Update to version 3.36.0 and your build will fail with org.json.JSONObject object expected, but com.chargebee.org.json.JSONObject provided.

Expected Behavior

I do not have to replace org.json.JSONObject with com.chargebee.org.json.JSONObject in my code when upgrading from version 3.35.0

Code Snippets (if applicable)

Operating System

any

Language version

Java 21

Library version

v3.36.0

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions