We're actually in a similar situation, it's unclear if/how much we'll be using jsonapi in the future. For the near/medium term though we have a fork targeting scala 2.12 and the circe module that we will be using while we nail down our direction going forward.
It doesn't cleanly patch into #64, but maybe there could be some helpful cross-pollination there?

Feels like jsonapi is losing traction lately. Mind sharing any insights on the why, or what you're replacing it with?

@oporkka Thanks for taking care of that. As a matter of fact we are using the library. Nevertheless it is not advised to use it inside Zalando for new services. I'll focus on bringing it to version 1.0 since it will help me and my pet projects.

@nkgm I have impression that people are moving away from REST in general (to grpc and others). In the REST world using non-jsonapi structures feels like more freedom and less overhead. Also one of main concerns about jsonapi is that is not back and forth compatible with non-jsonapi (you have to (un)wrap all the attributes in data path - we always ended up with the question WHY?).

This is my 5 cents on that. :)

@zmeda It seems as though this library has been quiet for some time. I do still find myself using the features in scala-jsonapi from time to time and, as of this writing, there is a fairly recent PR by @yvoderatskyi here. If there aren't any objections, perhaps @yvoderatskyi and I could take over the role of maintaining this project?

@franklinchou I added you now.

@oporkka @franklinchou could you include me as well?

@yvoderatskyi done!