Skip to content

Rewrite/Refactor parts of RESTClient impl. #2022

@syncblaze

Description

@syncblaze

Summary

There is a lot of inconsistency which build up over the last few years in the way the diffrent rest methods are implemented. One big inconsistency for example is handling value of function parameters.
I will leave a example for this here you can see that the None & undefined check is doubled.
IMG_0192

Requirements

#2021 needs to be merged first before this can makes sense doing

Why is this needed?

Consistency is nice and doubled checks are bad for developer expierence and prob a small bit performance.

Ideal implementation

Looking through most of the rest functions and refactor some of them where needed.

Checklist

  • I have searched the issue tracker and have made sure it's not a duplicate. If it is a follow up of another issue, I have specified it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions