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
container.In and container.Out allow using struct fields for dependency provide inputs and outputs.
If an unexported field is in one of these structs, the container still tries to use it and go just panics.
The container should report an error and tell the user which field is the problem. We could consider just skipping unexported fields, but this might lead to more unexpected behavior. Probably better to keep the current behavior but improve the error message.
The text was updated successfully, but these errors were encountered:
aaronc
changed the title
Better handling of unexported fields with container.In/Out
Better error for unexported fields with container.In/Out
May 11, 2022
container.In
andcontainer.Out
allow using struct fields for dependency provide inputs and outputs.If an unexported field is in one of these structs, the container still tries to use it and go just panics.
The container should report an error and tell the user which field is the problem. We could consider just skipping unexported fields, but this might lead to more unexpected behavior. Probably better to keep the current behavior but improve the error message.
The text was updated successfully, but these errors were encountered: