Skip to content

Issues with the command Process JSON #3657

Description

@Mimigris

The command currently encounters the following crashes:

  • Using Process JSON: Set Value on a source JSON that only has a value (e.g. "string", 1, 1.234, null, false, true, with nothing else) crashes the Player
  • Using Process JSON: Set Value on a sub-object that does not exist while the object exists but has a value set crashes the Player (e.g. if you have {"test_example":"test"} as your json and attempt to edit /test_example/hello which should edit the sub-object hello of test_example, the Player will crash)

Some warnings can be displayed on top of each other, making it harder to understand what is happening
Image

When a string variable stores a JSON on one line with no space, it can be hard to read it as the pretty print option is not always present and automatic line jumps will not work, may want to adjust some parameters.
Image

Improvement ideas:

  • Using Process JSON: Get Value on a boolean always returns OFF for a switch and 0 for a variable, would make sense to return OFF/ON and 0/1 depending on the type. Similarly, Returning true or false as a boolean when using a switch for Process JSON: Set Value could be an idea.

Metadata

Metadata

Assignees

No one assigned

    Labels

    CrashEasyRPGNew functionality exclusive to EasyRPG PlayerEvent/InterpreterUXFor issues affecting the user experience, such annoyances, counter-intuitive or ugly design

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions