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
In my journey to learn KotlinJS I've created a small pet project with some examples, using the most up to date version of the wrappers available today (February 4th, 2023). I believe this is important as some example projects out there still use the legacy React wrappers, or they are too small or too big, or they use very outdated versions of the wrappers which is problematic as some apis have suffered some changes recently. Also I tried to write a lot of comments trying to explain the intention and reason for doing things the way I do and to warn about some pitfalls.
I'd like to share this project in case it might be useful to anyone.
First of all, thank you very much for reviewing my code.
As per @turansky indications, I changed tabs into spaces and added Margin function.
Also changed the usage of StateInstance class to a newly created interface which removes the coupling such usage created. I assume that this was the reason why it was considered it an antipattern, is it correct?
In my journey to learn KotlinJS I've created a small pet project with some examples, using the most up to date version of the wrappers available today (February 4th, 2023). I believe this is important as some example projects out there still use the legacy React wrappers, or they are too small or too big, or they use very outdated versions of the wrappers which is problematic as some apis have suffered some changes recently. Also I tried to write a lot of comments trying to explain the intention and reason for doing things the way I do and to warn about some pitfalls.
I'd like to share this project in case it might be useful to anyone.
https://github.com/jfontsaballs/KotlinJsReactPatterns
The text was updated successfully, but these errors were encountered: