rhuss opened a new issue, #925: URL: https://github.com/apache/camel-kamelets/issues/925
Since Twitter IDs as unsigned 64-bit integer values that [cannot be handled fully by JavaScript](https://github.com/Twitter4J/Twitter4J/pull/276#issuecomment-1125688911), the exposed `id` field as integer can not be sealed with JavaScript. [Twitter has a `id_str` field in its REST API](https://developer.twitter.com/en/docs/twitter-ids), however Twitter4J does not add this field to its response. Also, since [Twitter4J](https://github.com/Twitter4J/Twitter4J/pull/276) seems to refuse to add this field, it would be great if Camel could re-add it to its components. I will create an issue in the Camel JIRA for this, but for now, a quick fix for kamelets would be to add the long value as a string with key "id_str" in the kamelets, too, until the component update bubbles up. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
