You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For content without the flex key, the SDK automatically adds flex: 0 to the component attribute. However, flex:0 could break the design.
I don't know if the behavior in the SDK is a bug or if it was added out of kindness, but I suggest not adding this key.
(FYI, until the fixed build comes out, you can add flex: 999 to those components without flex as a temporary solution.
Thank you for using the messaging API and the line-bot-sdk-go.
We apologize for the delayed response.
The behavior you're experiencing is due to the fact that FlexText.Flex is of the int32 type, which defaults to 0. Using a pointer type for int32 would allow us to distinguish between null and 0, but this would result in a breaking change to the SDK's specifications.
For the time being, as you suggested, please specify a value like flex:999 to work around the issue.
We apologize for any inconvenience this may cause.
Thank you for your patience.
System Informations
Expected Behavior
Here is a simple Flex message I design with the Flex Message Simulator tool
and the message should look like this
Current Behavior
Here is part of my Golang code
and the sent image looks like this
The align format is quite different from the expected one.
Steps to Reproduce
Logs
No obvious error log
The text was updated successfully, but these errors were encountered: