I think it supports scalameta now
Yeah. I would like to migrate to scalameta, but the feature set isn't quite there yet to support what we're doing
that would allow for the resolution of the error on
primaryKey
for instance, something where you could write
User.dprops.username[Username] instead 0f User.props.username
so you would have to supply the type manually, and dynamic methods have a minor runtime overhead.. and you could get a runtime error if the types don't match
aaah yeah, the more you do on shapeless the better
Sorry, what I wanted to say is that maybe you can not only see how shapeless does this, but do more things with shapeless than with macros
Okay, I'm going to install IDEA and take a look
the whole project is awesome
One question I was curious about, there’s no support for inheritance in the persisted case classes props, like this for instance:
@persistent[DomainModel]
case class User(
username: Username,
email: Email,
fullName: FullName,
answers: List[Answer] = Nil
)
trait Answer
@component[DomainModel]
case class AAnswer(a: String) extends Answer
@component[DomainModel]
case class BAnswer(b: Int) extends Answer
in a project I am about to start for a customer
Looks like this is the thing to use to get IDEA to understand the macros: https://blog.jetbrains.com/scala/2015/10/14/intellij-api-to-build-scala-macros-support/
all those links are in this dir: https://github.com/JetBrains/intellij-scala/tree/idea172.x/src/org/jetbrains/plugins/scala/lang/psi/impl/toplevel/typedef
Here's my longevity about IDEA support: longevityframework/longevity#36
issue that is
@mardo I would be thrilled if you wanted to try either of the approaches I mention in the ticket. Of course the IDEA API approach would be best, but it's going to be a good bit of work, and I'm not even sure up front if their API is flexible enough to make it happen
The "workaround" approach I describe in the ticket would be much more straightforward.
It puts a minor ugly into the longevity API (a method in
PType that's not very typesafe), but I'm okay with that. We can put a disclaimer in the scaladocs
It is really a IDE limitation, not really a framework one. However, a lot of people is using IntelliJ, so maybe the IDEA API approach is the best fit here. I’ll have a look when I have a chance
otherwise, as I said earlier, is not huge deal… it is just happening in the companion objects when defining the indexes (primary keys, keys, and so on…)
;)
IDEA is showing errors in other places for me as well. For instance on
and here: https://github.com/longevityframework/simbl/blob/master/src/main/scala/simbl/service/UserServiceImpl.scala#L116
User.queryDsl and User.props here: https://github.com/longevityframework/simbl/blob/master/src/main/scala/simbl/service/UserServiceImpl.scala#L35and here: https://github.com/longevityframework/simbl/blob/master/src/main/scala/simbl/service/UserServiceImpl.scala#L116