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
An external user of that package can set Payload, but it is always stored in serialized form.
Currently, it is not possible due to check in reform tool: Message has non-exported field body with "reform:" tag, it is not allowed. But we don't have a reason for that check anymore – generated code can access this field directly, no reflection (which almost always works only for exported fields) is required.
The text was updated successfully, but these errors were encountered:
@AlekSi I'm afraid, I'm not 100% understand the problem. What is the goal? Is the idea that an external user can set a field in a very "generic" form (interface{}) but wants to serialize it in a specific manner before insert? Could you give me an example? Smth about JSONB fields in Postgres?
I'd say this implementation look like "костыль" a little bit but on the other hand it gives some flexibility. Let me think about it a little bit.
Consider the following code:
An external user of that package can set Payload, but it is always stored in serialized form.
Currently, it is not possible due to check in
reform
tool:Message has non-exported field body with "reform:" tag, it is not allowed
. But we don't have a reason for that check anymore – generated code can access this field directly, no reflection (which almost always works only for exported fields) is required.The text was updated successfully, but these errors were encountered: