Closed lukasz-kusek closed 3 months ago
@lukasz-kusek may I kindly ask to check whether prism generation also suffers from this problem? Since you already know the background, it might be easy to check all cases in one go.
@lukasz-kusek may I kindly ask to check whether prism generation also suffers from this problem? Since you already know the background, it might be easy to check all cases in one go.
Sure. I think it doesn't suffer from the exact same problem, but thinking about it there might be similar one. Let me see.
@lukasz-kusek may I kindly ask to check whether prism generation also suffers from this problem? Since you already know the background, it might be easy to check all cases in one go.
Sure. I think it doesn't suffer from the exact same problem, but thinking about it there might be similar one. Let me see.
As I expected it had that problem, but not for parameters only for subclass name.
@serras Does this look ok now?
Very nice, I was just waiting for the CI to kick in and check that everything passes. Merging now.
@serras thanks
@serras when's the next release planned for?
Data classes which use parameters that have names which are Kotlin keywords and need to be escaped fail to compile:
This change makes generation of isos an lenses work with such parameters.
There's an additional test added that requires some additional fix in the code which is outside of the scope of this change.