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
Hi team, I'm new to scalaz so bare with me.
We are working with scalaz optionT transformers and are using the following conventions:
def doSomething(...): OurState[Unit] = {
(for {
x <- get[X].liftM[OptionT]
And getting the following errors on scaladoc
* What went wrong:
Execution failed for task ':paygrid-core:scaladoc'.
> Document failed because of an internal documenter error (Document failed with 3 errors; see the documenter error output for details.); see the error output for details.
[ant:scaladoc]..: error: value liftM is not a member of scalaz.State[com..state.X,...com..state.X]
[ant:scaladoc] x <- get[X].liftM[OptionT]
However, this may not be the culprit. I'd like to explore all possible avenues and hoping to gain some insight here if there may be something on the scalaz side (or perhaps we're not using the notations right)
scalaz: v 7.3.1
scala: 2.12.11
And we are using the following two imports:
import scalaz.Scalaz._
import scalaz._
Thanks in advance!
The text was updated successfully, but these errors were encountered:
Hi team, I'm new to scalaz so bare with me.
We are working with scalaz optionT transformers and are using the following conventions:
And getting the following errors on
scaladoc
At first glance, we had thought it may have been to do with this StackOverFlow issue: https://stackoverflow.com/questions/42684101/scaladoc-generation-fails-when-referencing-methods-generated-by-annotation-macro which links to the following scala issue: scala/bug#7993
However, this may not be the culprit. I'd like to explore all possible avenues and hoping to gain some insight here if there may be something on the scalaz side (or perhaps we're not using the notations right)
scalaz: v 7.3.1
scala: 2.12.11
And we are using the following two imports:
Thanks in advance!
The text was updated successfully, but these errors were encountered: