[Feature]: Change CustomData to map[string]string

[goenning]

Tell us about your feature request

Why is CustomData a map[string]any if the value is always a string?

What problem are you looking to solve?

Changing it to map[string]string would make it easier to use

Additional context

No response

How important is this suggestion to you?

Nice to have

[davidgrayston-paddle]

Hi @goenning 👋 Thank you for raising this issue.

The SDK currently reflects the API specification, which allows any object for custom_data (API Spec):

custom_data:
  title: Custom data
  type: object

If at any point in future this changes in the API, it would be reflected in the SDK.

[goenning]

how do I set custom_data values as numbers?

[davidgrayston-paddle]

In Go, the custom data could be created as follows:

paddle.CustomData{
	"key1": "string value",
	"key2": 1,
	"key3": 1.2,
}

The resulting JSON object would look like this:

{
    "key1": "string value",
    "key2": 1,
    "key3": 1.2
}

[goenning]

My use case is that I have defined custom data on a “Product” via Paddle.com, and it seems like via the UI only strings are supported?

[goenning]

When I get the webhook requests, the custom data values are always Strings

[davidgrayston-paddle]

Hi @goenning 👋

The paddle.com dashboard currently only supports creation/update of custom data with string values. However, nested custom data (with different value types) can be created via the API (using SDK), which is currently readonly in the dashboard. The dashboard will support nested custom data in future.