♻️ Remove JsonObject from return value

[devenyantis]

Description

Some return values are changed. Some remain as json object. Also added steps to handle fail cases to map the functionality of frontend.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Bug fix (Non-breaking change which fixes an issue)
• New feature (Non-breaking change which adds functionality)
• Breaking change (Fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update (Example: REST API changes)

Tested on?

• Windows
• Linux Ubuntu
• Centos
• Mac
• Others (State here -> xxx )

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged
• CHANGELOG.md has been updated
• Update Gitbook REST API Page

[treo]

A few comments here. I've only put them on the first place I noticed something, even when it applies to multiple places.

[treo]

A few more comments. Again they apply in a few cases, but I didn't put them everywhere, as it is pretty obvious where the same pattern repeats.

[treo]

I think you should be able to use the object mapper in a few more places to deserialize directly, instead of manually pulling data from a JsonObject or JsonArray

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

No Coverage information
0.0% Duplication