Mock (lazy) vals about scalamock HOT 5 CLOSED

This is expected behaviour because Scala doesn't allow a lazy val to be overridden with a def. It's possible that I might be able to make it work in ScalaMock4, however, which I've just started working on.

from scalamock.

This is now mentioned as a known limitation in the FAQ: http://scalamock.org/user-guide/faq/

from scalamock.

There is a comment from @paulbutcher on StackOverflow about scalameta making this possible. Is this now something that could be implemented?

from scalamock.

ScalaMeta is an interesting library but it will require significant rewrites to make use of it. ScalaMock relies on whitebox macros internally, which aren't exactly compatible and we'd need to transition away from that. Still worth looking at.

from scalamock.

a Scala val cannot be overridden by a def, so this feature doesn't fit into ScalaMock really, even with the potential use of ScalaMeta. Assuming the val is not final, you can just subclass it yourself so i don't really see a strong argument for ScalaMock to provide special handling. Example:

class ClazzIWantToMock {
  val thingIdlikeToOverride: Int = 5
}

class MockedClazz extends ClazzIWantToMock {
  override val thingIdlikeToOverride= 99
}

from scalamock.