Renaud Lienhart on Nostr: Now there are still some pitfalls to be aware of. Firstly, stay the hell away from ...
Now there are still some pitfalls to be aware of.
Firstly, stay the hell away from List; Nothing good ever comes out of this forsaken component.
Then -- and I know it's tempting -- you should really avoid GeometryReader if you can. Nowadays there are lots of better alternatives , e.g. ViewThatFits or the Layout protocol.
Be mindful of your Identifiable conformances! Things can go very, very wrong if the IDs are not truly unique.
Lastly, use composability to its maximum potential.
Firstly, stay the hell away from List; Nothing good ever comes out of this forsaken component.
Then -- and I know it's tempting -- you should really avoid GeometryReader if you can. Nowadays there are lots of better alternatives , e.g. ViewThatFits or the Layout protocol.
Be mindful of your Identifiable conformances! Things can go very, very wrong if the IDs are not truly unique.
Lastly, use composability to its maximum potential.