I've been working on improving the Elixir package for interacting with the Chargebee API and have encountered some inconsistency in how the different libraries construct POST request parameters
When I try to serialize a nested nested lists, as one would use when creating coupons, the serializers produce differing output depending on the library implementation.
Chargebee-Ruby produces the following
ChargeBee::Util.serialize({item_constraints: [{item_price_ids: ['id1']}]})
=> {"item_price_ids[0]"=>"id1"}