Also a great video. Have you thought of making an override for the image init that takes your newly created SFSymbol type? That way you could hide the internal detail of the raw value and have a nice call point. Image(sfSymbol: .arrowRight) Maybe a bit swiftier and having code completion to help you find the image name. Perhaps the macro could contain an extension on Image where you made this init with SFSymbol. What is your opinion on this? Am I guessing ahead at the next video already? ;)
Also a great video. Have you thought of making an override for the image init that takes your newly created SFSymbol type? That way you could hide the internal detail of the raw value and have a nice call point. Image(sfSymbol: .arrowRight) Maybe a bit swiftier and having code completion to help you find the image name. Perhaps the macro could contain an extension on Image where you made this init with SFSymbol. What is your opinion on this? Am I guessing ahead at the next video already? ;)
I like that idea. As we used to say in my academic teaching days, "that will be left as an exercise to the reader". Thank you