We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API returns timestamp as int64 type for "RichTextSectionDateElement" and json parsing fails.
The API response is correctly Unmarshalled into RichTextSectionDateElement.
Attached is the archive with the API output and a main.go program that, if executed, reproduces the error.
The attached archive contains also bug119-r.json which is the raw output from the API with the PII removed.
bug119-r.json
rich_text_date_issue.zip
manifest WHO?
I'm not sure how to go about this - has there been an instance where timestamp is string for this RichText block element?
Original issue link: rusq/slackdump#119
The text was updated successfully, but these errors were encountered:
Possibly JSONTime will do the trick? (an additional branch for when input is a number would be needed)
JSONTime
Sorry, something went wrong.
Hey team, any chance this can be looked at?
It will be fixed in v0.12.
Successfully merging a pull request may close this issue.
What happened
API returns timestamp as int64 type for "RichTextSectionDateElement" and json parsing fails.
Expected behavior
The API response is correctly Unmarshalled into RichTextSectionDateElement.
Steps to reproduce
Attached is the archive with the API output and a main.go program that, if executed, reproduces the error.
The attached archive contains also
bug119-r.json
which is the raw output from the API with the PII removed.reproducible code
rich_text_date_issue.zip
manifest.yaml
manifest WHO?
Versions
Comments
I'm not sure how to go about this - has there been an instance where timestamp is string for this RichText block element?
Original issue link: rusq/slackdump#119
The text was updated successfully, but these errors were encountered: