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
This issue is also potentially connected with #1462.
Problem description:
When a .proto file contains a message with both a nested message field and a oneof field named option, the scalapb compiler generates an object Option and in the parseFrom method's pattern matching, it uses Option without specifying the Scala package (_root_.scala.Option). This causes the Scala compiler to produce an error, as it interprets Option as the generated object Option rather than the standard Scala Option, which does not take parameters.
This issue is also potentially connected with #1462.
Problem description:
When a
.proto
file contains a message with both a nestedmessage
field and aoneof
field named option, the scalapb compiler generates anobject Option
and in theparseFrom
method's pattern matching, it usesOption
without specifying the Scala package (_root_.scala.Option
). This causes the Scala compiler to produce an error, as it interpretsOption
as the generatedobject Option
rather than the standard Scala Option, which does not take parameters.Steps to reproduce:
PaymentMethod.proto
file with contents:.proto
fileobject PaymentMethod
within theparseFrom
function: "object Option in object PaymentMethod does not take parameters."The text was updated successfully, but these errors were encountered: