Use of locals() vague #7
Description
Considering changing how payloads are handled. Utilizing locals() allowed for some pretty code and less lines overall, but considering the number of possible arguments to many of the calls related to creation or editing of resources such as monitors, psp's, etc, it might be better to create separate classes representing each type of payload.
The classes could have as their attributes the possible arguments to the API call itself. This would demystify things a bit. More code, less concise. More readable, probably less prone to error. Likely going to start working on a refactor to support these ideas.