RichTextDate.Timestamp string type instead of long

[ulrichb]

The current implementation of RichTextDate uses a string type for Timestamp:

SlackNet/SlackNet/Blocks/RichTextBlock.cs

Line 96 in 9e94680

public string Timestamp { get; set; }

When using RichTextDate against the current Slack API, we're getting Slack error respones like this:

[ERROR] must provide an integer [json-pointer: /blocks/0/elements/1/elements/1/elements/1/timestamp

In the Slack docs also number is mentioned for timestamp: https://api.slack.com/reference/block-kit/blocks#date-element-type.

I've also tested with a custom RichTextSectionElement subtype with public long Timestamp and it works fine.

So I think we should change the type to long and also the corresponding ToTimestamp() helper.

[soxtoby]

Thanks for raising this @ulrichb. I'll change the Timestamp property to long, but since ToTimestamp is being used in places that still require a string, we'll need a new helper to get the long value - probably ToTimestampNumber, for lack of a shorter alternative.

I'll try to get a new release up in the next day or so with the fix for this.

[soxtoby]

Fix is now available in v0.17.2.

[ulrichb]

Many thanks for the very quick fix @soxtoby!