-
-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
interfaces' field description derived incorrectly #1951
Comments
Typeclass derivation doesn't give access to The workaround is to make a custom |
@ghostdogpr thank you for the clarification!
Do I understand correctly, that it is a restriction imposed by an upstream library (I guess Magnolia or something)? Even if it cannot be entirely supported, I suppose the experience can be improved quite a bit. Specifically, I'm thinking about two assumptions that IMO should be feasible to implement:
It would not be perfect of course, but I believe it would be way more intuitive to users and could support more real use cases without falling into manual schema adjustments. Also I feel it would be really helpful to have a new paragraph in the Schemas chapter (e.g. "Known Limitations") where users could read about issues like this one. |
Yep, that's right: Magnolia on Scala 2 and direct typeclass derivation on Scala 3. I agree with the heuristic proposed, and it should not be hard to implement. |
Consider a snippet:
Expected output:
Actual output:
The text was updated successfully, but these errors were encountered: