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
{{ message }}
This repository has been archived by the owner on Jun 1, 2024. It is now read-only.
As a user I want to create my Custom Components using Classes instead of Structs, and still would not need to manually create code for Decodable conformance.
Problem
We provide a tool to our users to automatically generate Decodable conformance for custom components. But that tool does not work with Classes, only Structs.
Expected behaviour
solution won't change how it works with Structs, only extend to also work with Classes
the API (AutoDecodable) should be the same
The text was updated successfully, but these errors were encountered:
theffc
added
iOS
This issue directly affects structure and logic of iOS project
DX
Dev Experience: something that directly degrades our users (developers) experience with our product
labels
Jun 12, 2020
Description
As a user I want to create my Custom Components using Classes instead of Structs, and still would not need to manually create code for
Decodable
conformance.Problem
We provide a tool to our users to automatically generate
Decodable
conformance for custom components. But that tool does not work with Classes, only Structs.Expected behaviour
AutoDecodable
) should be the sameThe text was updated successfully, but these errors were encountered: