Use payload as string instead of map #6
Conversation
|
@erikcardona Could you please fix the CI issues? |
|
@burntcarrot it should be fine now |
|
I thought about this decision, but I feel it would be a huge deal-breaker for someone who would be using the library, as moving payload to a string essentially renders the ease of use provided by this library obsolete. Having to encode the payload manually through escape characters is a cumbersome task, as it gets harder when the payload is large, and you need to manually add escape characters each time. I do understand the conflicts brought by Could you rethink the design? I'm refactoring some code to make the user experience much better in #7, if that interests you, please take a look. (spoiler: it still uses |
Reason:
I had issue from my project because of the version of poison dependency.
Solution:
Reduce dependency removing poison and change payload from map to string.