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
Thanks a lot for getting fixes out for #3380 and #3381 so fast in version 1.2.3! Now that we're able to start playing around with the Raise DSL, we've discovered another snippet of code that generates bad Kotlin code from Optics. (I'm sorry-not-sorry for doing this!)
Here, it's missing the type parameter for LoadingContentOrError.ContentOrError, which should be LoadingContentOrError.ContentOrError<Data>, not just LoadingContentOrError.ContentOrError. The correctly generated code would look like this:
Thanks a lot for getting fixes out for #3380 and #3381 so fast in version 1.2.3! Now that we're able to start playing around with the
Raise
DSL, we've discovered another snippet of code that generates bad Kotlin code from Optics. (I'm sorry-not-sorry for doing this!)Inspired by https://arrow-kt.io/learn/typed-errors/own-error-types/, we did something like this:
(We needed a type that represented only
Content
orError
, but notLoading
, whilst still being aLoadingContentOrError
.)However, unfortunately,
@optics
isn't too happy about the generic usage here, either, and gives generates the following code:Here, it's missing the type parameter for
LoadingContentOrError.ContentOrError
, which should beLoadingContentOrError.ContentOrError<Data>
, not justLoadingContentOrError.ContentOrError
. The correctly generated code would look like this:The text was updated successfully, but these errors were encountered: